Skip to content
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

Fix SQLite3 sequence handling #32

Open
schengawegga opened this issue Jan 18, 2024 · 1 comment
Open

Fix SQLite3 sequence handling #32

schengawegga opened this issue Jan 18, 2024 · 1 comment
Labels

Comments

@schengawegga
Copy link
Collaborator

In SQLite3 sequence table created automatically and store AI informations for all tables in only one sequence table, if AUTOINCREMENT is selected in a table.
Maybe create_sequence, drop_sequence, and sequence_name are not needed anymore, and nextId has to be changed to the new sequence table, or to work without sequence table.
Maybe AUTOINCREMENT is needed, because AI works if PRIMARY KEY is present, too.
Maybe AUTOINCREMENT is obsolet, because the field has to be PRIMARY KEY to select AUTOINCREMENT.

grafik

@schengawegga schengawegga added this to the Version 1.12.2 milestone Jan 18, 2024
@schengawegga
Copy link
Collaborator Author

It is not a bug. SQLite works with AUTOINCREMENT and ROWID. As an alternative, PEAR\DB supports his own sequence solution.
TODO: Check the correct behavior of the pear sequences.

@schengawegga schengawegga removed this from the Version 1.12.2 milestone Apr 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant