[MDEV-7332] sequence storage engine improvements Created: 2014-12-15  Updated: 2015-10-31

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - Sequence
Fix Version/s: None

Type: Task Priority: Major
Reporter: roberto spadim Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None

Issue Links:
Duplicate
duplicates MDEV-9050 Allow variables in SEQUENCE table names Closed

 Description   

1) Implement a signed sequence table
that's a bit ugly...
select * from `sseq_-1_to_-20_step_-1`
check the "s" before seq, that's because we are using signed variables, 'BIGINT SIGNED' instead of 'BIGINT UNSIGNED'

2) implement variables sequences using vars
that's a bit ugly too...
set @variable1=1234;
set @variable2=12340;
set @variable3=1;
select * from `vseq_variable_to_variable2_step_variable3`

in this case, NaN values should report a storage engine error, and we should think if we will have only unsigned values or not


Generated at Thu Feb 08 07:18:47 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.