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
Now, the following SELECT says the sqlite3 and the Firebird backends worked it out as I'd expected:
a
1
2
3
4
5
3
While dealing with MySQL and PostgreSQL DBMS and their soci backends I got the following results:
a
1
2
3
1
2
3
So, actually, after the first insertion portion something refuses to accept actually changed data as changed.
Could you please hint where to dig? (Or мaybe the problem lies on the surface?)
Thanks! The Firebird I used is 5. MySQL version is 8. The PostgreSQL is 14.
The text was updated successfully, but these errors were encountered:
This looks like a bug, to be honest. We even have a unit test checking that this works for scalar inserts, see "Multiple use and into", but not for vectors, unfortunately.
I'd have to debug it to see what's going on here...
OK! Look, if it's not too difficult.
Yes, I'd seen the code you pointed to, but I thought you run it against the sqlite3 only (which emulates the bulk).
If there were no problems with inserting scalars across all backends in this mode, then the error is probably somewhere during vector insertion.
As a helpful info: oracle and firebird backends for vectors works well. (maybe fixes for mysql and postgresql could be accomplished by analogy).
Hello,
Suppose, I have a trivial insertion code (much more simpler than the one, provided in the documention):
Now, the following SELECT says the sqlite3 and the Firebird backends worked it out as I'd expected:
While dealing with MySQL and PostgreSQL DBMS and their soci backends I got the following results:
So, actually, after the first insertion portion something refuses to accept actually changed data as changed.
Could you please hint where to dig? (Or мaybe the problem lies on the surface?)
Thanks!
The Firebird I used is 5. MySQL version is 8. The PostgreSQL is 14.
The text was updated successfully, but these errors were encountered: