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.

Sign up for GitHub

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

Jump to bottom

Consider whether support for any RDBMS can be dropped #5

Open
dieggsy opened this issue Mar 6, 2025 · 2 comments
Open

Consider whether support for any RDBMS can be dropped #5

dieggsy opened this issue Mar 6, 2025 · 2 comments

Comments

@dieggsy
Copy link
Collaborator

dieggsy commented Mar 6, 2025 •
edited
Loading

Not sure about this, since it would be nice to maintain as much backwards compatibility as possible. However:

  • I wonder if anyone's actually using some of these. For example:
    • Is there any benefit to sqlite over sqlite3? Is it still used?
    • Do we really need clsql-postgresql-socket and clsql-postgresql-socket3?
  • Less code makes this library easier to maintain and manage going forward.
@dieggsy
Copy link
Collaborator Author

dieggsy commented Mar 10, 2025

I'll note that the last release of sqlite2 was in 2005.

@dieggsy
Copy link
Collaborator Author

dieggsy commented Mar 11, 2025

It seems safe to drop SQLite2 - it's not even downloadable from sqlite.org

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dieggsy