Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rdbms: simple scenario - insert #15

Open
dcrissman opened this issue Mar 5, 2015 · 1 comment
Open

rdbms: simple scenario - insert #15

dcrissman opened this issue Mar 5, 2015 · 1 comment

Comments

@dcrissman
Copy link
Member

INSERT INTO MY_TABLE (MY_DATE, MY_NUMBER, MY_VARCHAR2)
);
[
{
"operation": "insert_row",
"table": "my_table",
"columns": [
"$non_null_columns"
]
}
]

This example uses "$non_null_columns", but it leaves me wondering what that value means? It also leaves me wondering what happened to the inserted values?

@bserdar
Copy link
Contributor

bserdar commented Mar 5, 2015

It is not completely specifiied yet but $non_null_columns will be derived
from field/column mappings, and include all non-null column names and
values. It will be up to the dialect to interpret that list of
column/values, and write the INSERT statement.

On Thu, Mar 5, 2015 at 9:50 AM, Dennis Crissman [email protected]
wrote:

INSERT INTO MY_TABLE (MY_DATE, MY_NUMBER, MY_VARCHAR2)
);
[
{
"operation": "insert_row",
"table": "my_table",
"columns": [
"$non_null_columns"
]
}
]

This example uses "$non_null_columns", but it leaves me wondering what
that value means? It also leaves me wondering what happened to the inserted
values?


Reply to this email directly or view it on GitHub
#15.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants