From: Steve Ebersole on behalf of Steve Ebersole
> So certainly we could have SequenceGenerator account for trimming the sequence
> name. I obviously have no objections to that.
>
> As for not not creating the dual_* tables:
> 1) I do not like (and will not code for) a "MY_COMMON_DUAL" approach; this is
> a simple oversight in HSQLDB (at least "back then", #2 alleviates that
> shortcoming)
> 2) since when was the "call NEXT VALUE FOR [sequence_name]" syntax available?
> Depending on the answer to that, I have no issues with going this route;
> create a patch and attach to a JIRA request.