-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Accept pipeline input for stor insert
values
#11433
Comments
I'd support that. It should be pretty easy to do. You just have to check for I'm all for making these |
Hi, me and my colleague would like to know if it is still possible to work on this enhancement! |
@JoaoFidalgo1403 Sure. I was just thinking that it could work both ways. If the |
@fdncred Also, would it be ok if we did the same work on |
i think so |
Would something like this be on the right track? I'm new to the code base and a little unfamiliar with the code style. |
@bobby-palmer I think that's probably part of it, although |
Related problem
While it's been established that
into sqlite
's ability to append to a database is more a "side-effect" than part of its design, it seems so much simpler thanstor insert
. For example, with a REST call that returns a JSONitems
with a list of records (i.e. a Nu table):With
into sqlite
:This currently works when both creating the database as well as updating, as long as the values match their original positions.
With
stor insert
:(^ from memory - Hope I got those right)
Describe the solution you'd like
Allow
stor insert
to accept pipeline input in the form of either a record:In the second case, I'm guessing the column names would need to be inferred from the first record, which
into sqlite
seems to do when creating (but not updating) the database (to support streaming). Any change in the signature of future records would result in an error.Describe alternatives you've considered
No response
Additional context and details
Would this also work for
stor update
?The text was updated successfully, but these errors were encountered: