Sqlite.swift: Is this project alive?

[pgawlowski]

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.

[newtimber]

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.

[juanjoseluisgarcia]

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

[Quailcreek]

Hi juanjoseluisgarcia,
I'm looking at converting several of my apps from SQLite.swift to GRDB. Would you be willing to give me a hand getting stared?

[newtimber]

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.

[juanjoseluisgarcia]

@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.

[Quailcreek]

Thank you, juanjoseluisgarcia. After beating my head against the monitor I have come to the same conclusion.