You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It can be useful to allow the API users to indicate that there are unique constraints when building a Table.
For example, one may want to use Splout for generating a SQL store out of a set of registers that were appended to a big file (e.g. HDFS). Sometimes it could happen that a register with the same "id" was appended twice or more times. In this case, the user probably doesn't want to have duplicates in the final table.
The opened question is how this should be handled. I see two possible ways:
Letting SQLite handle unique constraints, and catching the exception.
Handling the unique constrain before inserting to SQLite. This could probably be done using the specific OrderBy (InsertionOrderBy) that can now be used to sort the data before appending it to SQLite, but it is unclear.
The text was updated successfully, but these errors were encountered:
For these cases, something important is which version should survive. User
probably would like a oarticular versions to survive, based on some policy.
Possible policies would be:
Insertion order. Last/first one survive. Easy to handle by the use of
InsertionOrderBy
Based on some kind of timestamp... but maybe the used don't want to
insert the timestamp in the final table. (some kind of hidden column)
It can be useful to allow the API users to indicate that there are unique
constraints when building a Table.
For example, one may want to use Splout for generating a SQL store out of
a set of registers that were appended to a big file (e.g. HDFS). Sometimes
it could happen that a register with the same "id" was appended twice or
more times. In this case, the user probably doesn't want to have duplicates
in the final table.
The opened question is how this should be handled. I see two possible ways:
Letting SQLite handle unique constraints, and catching the exception.
Handling the unique constrain before inserting to SQLite. This could
probably be done using the specific OrderBy (InsertionOrderBy) that can now
be used to sort the data before appending it to SQLite, but it is unclear.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10.
It can be useful to allow the API users to indicate that there are unique constraints when building a Table.
For example, one may want to use Splout for generating a SQL store out of a set of registers that were appended to a big file (e.g. HDFS). Sometimes it could happen that a register with the same "id" was appended twice or more times. In this case, the user probably doesn't want to have duplicates in the final table.
The opened question is how this should be handled. I see two possible ways:
The text was updated successfully, but these errors were encountered: