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
Postgresql executes a Sequence, returns nextval, whether or not "optional" is set
Postgresql renders the "nextval" construct, whether or not "optional" is set
func.next_value().execute()/.scalar() works
Using a DefaultGenerator in the columns, where clause of a select, or in the values clause of insert, update, raises the informative error
Same for Sequence, test the additional string
can use next_value() in:
select column expr
whereclause
values of insert/update
return of next_value is an int, check oracle
insert statement:
inserted_primary_key contains the result when pk_col=next_value(), when implicit returning is used, when not used, it should be none. probably want to put this in test_returning
next_value() used on non-sequence platform either raises NotImplemented, or perhaps we determine some other kind of placeholder
Migrated issue, originally created by Michael Bayer (@zzzeek)
i.e. next_value(some_seq), more usefully apply it to Sequence, some_seq.next_value()
this is somewhat major since we'd be using this construct internally as well for consistency.
Attachments: ticket_2084_2085.patch
The text was updated successfully, but these errors were encountered: