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

Getting rid of the sqlite3 gem (for shoes4) #159

Open
PragTob opened this issue Apr 24, 2013 · 3 comments
Open

Getting rid of the sqlite3 gem (for shoes4) #159

PragTob opened this issue Apr 24, 2013 · 3 comments

Comments

@PragTob
Copy link
Member

PragTob commented Apr 24, 2013

In the future, hacketyhack shall work with shoes4. That's what we are working for.

However currently it uses the sqlite3 gem in `lib/database.rb', which is a problem because it needs c-extensions. That is a problem as jruby cut c-extension support.

From a first look it should be easy to replace sqlite with something else, I'd say Pstore or YAML::Store as the interface is tiny and well defined.

We would just have a problem with the migration of old user data. We could also use a jruby gem for sqlite3, if there is one. However, I'd much rather use the simple file based standard library functionality as mentioned above.

Thoughts?

@plexus
Copy link

plexus commented Apr 25, 2013

At first glance there's no sqlite3 ffi gem, although some people have
worked on porting it.

Less dependencies is better though so I think it's a good idea, but there
would have to be a conversion script as well.
On Apr 24, 2013 11:50 PM, "Tobias Pfeiffer" notifications@github.com
wrote:

In the future, hacketyhack shall work with shoes4. That's what we are
working for.

However currently it uses the sqlite3 gem in `lib/database.rb', which is a
problem because it needs c-extensions. That is a problem as jruby cut
c-extension support.

From a first look it should be easy to replace sqlite with something else,
I'd say Pstore or YAML::Store as the interface is tiny and well defined.

We would just have a problem with the migration of old user data. We could
also use a jruby gem for sqlite3, if there is one. However, I'd much rather
use the simple file based standard library functionality as mentioned above.

Thoughts?


Reply to this email directly or view it on GitHubhttps://github.com//issues/159
.

@steveklabnik
Copy link
Member

Don't you just use jdbc-sqlite3?

@PragTob
Copy link
Member Author

PragTob commented Jun 28, 2013

Just a note, that we basically have Steve's ok on this :-D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants