-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Is this project alive? #1031
Comments
I wouldn't start a new project with it; but if you're already using it and the issues don't effect you, then continue using it as it's a lot of work to change to something else. |
I was using it and got rejected on the app store because the app was unstable with 'database locked' error messages. I switched to GRDB.Swift |
Hi juanjoseluisgarcia, |
I'm just in the progress of converting and finding it very time consuming as for backwards compatibility, you have to keep the database structures the same and all the indentations are different as you have to indent the code more with GRDB. Added to which you have to convert entire projects at once as you cannot have GRDB and SQLite running at the same time. In retrospect, it would have been a better use of my time to copy the SQLite code and support that myself rather than spending hours converting existing projects to GRDB. |
@Quailcreek @newtimber My suggestion for migrating from SQLite.Swift to GRDB is to use the SQL 'flavour' of the library. That is the one that allows us not to rewrite the entire database and it is the quickest path when migrating. I have found. |
Thank you, juanjoseluisgarcia. After beating my head against the monitor I have come to the same conclusion. |
Hello, I joined the SQLite.swift maintainers team, and we're going to merge pull requests and fix issues in the coming days. (Already a few were merged at time of writing, and we are replacing the outdated travis CI with GitHub Actions) |
Sorry but I couldn’t wait. I have already switched to GRDB.
…On Wed, Aug 18, 2021 at 1:57 PM Nathan Fallet ***@***.***> wrote:
Hello, I joined the SQLite.swift maintainers team, and we're going to
merge pull requests and fix issues in the coming days. (Already a few were
merged at time of writing, and we are replacing the outdated travis CI with
GitHub Actions)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1031 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADLCZPBIDFWSREMY2RIGEJDT5QNB3ANCNFSM4TR3NA5A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
this project has been dead a few times. so far it's always come back. |
Last update: year ago
25+ issues from this year
Bunch of issues with new xcode.
Bunch of pull requests, all failing on travis.
Lack of communication.
My only question is: is this project alive? Cause I do not want to relay on something that is already dead and is causing a lot of trouble to handle.
The text was updated successfully, but these errors were encountered: