[damagecontrol-user] sqlite3 hassles

[Chad Woolley]

I'm trying to get DamageControl running on my server (WBEL3).  I had problems with this error: [1]

I had to build sqlite3 from source, which was a pain itself because tcl isn't installed on WBEL3 [2].

I finally got it built, and now I have libsqlite3.so.  Then, I had to copy it to about a half dozen locations on my system before rails would finally find it.

I'm wondering why sqlite3 is required rather than just plain sqlite 2 (which would have been easy to install, since it is on most apt repos)?  If this is possible, it might prevent other users from having the hassles I have, at least until sqlite3 is in prevalent usage.

Just a suggestion,
Chad

[1] libsqlite3.so: cannot open shared object file: No such file or directory

[2] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=116687

[Aslak Hellesoy]

hi chad!

you dhould be able to use any active-record compliant database:
postgresql, mysql, sqlite2/3 etc. just edit your database.yml file
according to rails' doco for activerecord and run rake migrate.

it's just that the default config is for sqlite3 - you're free to
change it to what you like.

aslak

On 11/5/05, Chad Woolley <thewoolleyman@...> wrote:

> I'm trying to get DamageControl running on my server (WBEL3).  I had
> problems with this error: [1]
>
>  I had to build sqlite3 from source, which was a pain itself because tcl
> isn't installed on WBEL3 [2].
>
>  I finally got it built, and now I have libsqlite3.so.  Then, I had to copy
> it to about a half dozen locations on my system before rails would finally
> find it.
>
>  I'm wondering why sqlite3 is required rather than just plain sqlite 2
> (which would have been easy to install, since it is on most apt repos)?  If
> this is possible, it might prevent other users from having the hassles I
> have, at least until sqlite3 is in prevalent usage.
>
>  Just a suggestion,
>  Chad
>
>  [1] libsqlite3.so: cannot open shared object file: No such file or
> directory
>  [2]
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=116687
>
>
>

[Chad Woolley]

OK.  I like sqlite, I'll try to use v3 since I have it working now.  Well, maybe.  I get this error when running rake migrate with a new checkout:

rake aborted!
undefined method `quote' for SQLite3::Database:Class

I assume this is something unsupported for sqlite?  However, its strange for this to happen if sqlite3 is the default.

Any hints on what this is or where to start debugging?  If it's not too hard, I can try to patch it.

Thanks for the response,
Chad

On 11/5/05, aslak hellesoy <aslak.hellesoy@...> wrote:

hi chad!

you dhould be able to use any active-record compliant database:
postgresql, mysql, sqlite2/3 etc. just edit your database.yml file
according to rails' doco for activerecord and run rake migrate.

it's just that the default config is for sqlite3 - you're free to
change it to what you like.

aslak

On 11/5/05, Chad Woolley <thewoolleyman@...> wrote:

> I'm trying to get DamageControl running on my server (WBEL3).  I had
> problems with this error: [1]
>
>  I had to build sqlite3 from source, which was a pain itself because tcl
> isn't installed on WBEL3 [2].
>
>  I finally got it built, and now I have libsqlite3.so.  Then, I had to copy
> it to about a half dozen locations on my system before rails would finally
> find it.
>
>  I'm wondering why sqlite3 is required rather than just plain sqlite 2
> (which would have been easy to install, since it is on most apt repos)?  If
> this is possible, it might prevent other users from having the hassles I
> have, at least until sqlite3 is in prevalent usage.
>
>  Just a suggestion,
>  Chad
>
>  [1] libsqlite3.so: cannot open shared object file: No such file or
> directory
>  [2]
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=116687
>
>
>

[Chad Woolley]

Some parts of this message have been removed. Learn more about Nabble's security policy.

FYI, this error doesn't occur with the regular sqlite (v2) driver specified...

On 11/5/05, Chad Woolley <thewoolleyman@...> wrote:

OK.  I like sqlite, I'll try to use v3 since I have it working now.  Well, maybe.  I get this error when running rake migrate with a new checkout:

rake aborted!
undefined method `quote' for SQLite3::Database:Class

I assume this is something unsupported for sqlite?  However, its strange for this to happen if sqlite3 is the default.

Any hints on what this is or where to start debugging?  If it's not too hard, I can try to patch it.

Thanks for the response,
Chad

On 11/5/05, aslak hellesoy <aslak.hellesoy@...> wrote:

hi chad!

you dhould be able to use any active-record compliant database:
postgresql, mysql, sqlite2/3 etc. just edit your database.yml file
according to rails' doco for activerecord and run rake migrate.

it's just that the default config is for sqlite3 - you're free to
change it to what you like.

aslak

On 11/5/05, Chad Woolley <thewoolleyman@...> wrote:

> I'm trying to get DamageControl running on my server (WBEL3).  I had
> problems with this error: [1]
>
>  I had to build sqlite3 from source, which was a pain itself because tcl
> isn't installed on WBEL3 [2].
>
>  I finally got it built, and now I have libsqlite3.so.  Then, I had to copy
> it to about a half dozen locations on my system before rails would finally
> find it.
>
>  I'm wondering why sqlite3 is required rather than just plain sqlite 2
> (which would have been easy to install, since it is on most apt repos)?  If
> this is possible, it might prevent other users from having the hassles I
> have, at least until sqlite3 is in prevalent usage.
>
>  Just a suggestion,
>  Chad
>
>  [1] libsqlite3.so: cannot open shared object file: No such file or
> directory
>  [2]
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=116687
>
>
>