Thanks Jonathan - that's done the trick.
(BTW my previous fumble was an attempt to pinpoint my problem by
connecting without Camping.)
With the idea of using this as the simplest possible 'Camping with
SQLite' example for beginners (or testing new setups), I've adjusted
and pastied it: ht
On Tue, Jun 09, 2009 at 11:35:26AM +0100, Dave Everitt wrote:
Any feedback appreciated on the following. My most recent attempt to
identify the issue is a minimal Ruby/SQLite/ActiveRecord script, Pastied
here: http://pastie.textmate.org/492514 which brings up the following
when run from the co
Dave - to answer:
1. sqlite3-ruby (1.2.4),
2. I installed an updated Ruby (1.8.6) some time ago (can't recall
how!),
3. sqlite3 (3.1.3) is already on OS X 10.4.11,
4. I don't use a package manager (or ports or fink), and know nothing
about sqlite header files. I was thinking of installing a
Increasing permissions (currently 755) makes no difference. I can use
the DB fine from the sqlite3 cl tool - Dave
On 9 Jun 2009, at 13:26, Eric Mill wrote:
Are the permissions on the file set right? What happens if you try
to access the file with rhe sqlite3 command line tool and run the
What version of the gem are you using? 1.2.4? I'm assuming you
compiled ruby yourself based off of its location, did you compile
sqlite as well or get it through your OS package manager? In either
case, I've found you'll need the sqlite header files for the gem to
work correctly. In your package ma
Are the permissions on the file set right? What happens if you try to
access the file with rhe sqlite3 command line tool and run the query
yourself?
-- Eric
On Tue, Jun 9, 2009 at 6:35 AM, Dave Everitt wrote:
> Any feedback appreciated on the following. My most recent attempt to
> identify the is
Any feedback appreciated on the following. My most recent attempt to
identify the issue is a minimal Ruby/SQLite/ActiveRecord script,
Pastied here: http://pastie.textmate.org/492514 which brings up the
following when run from the command line (an empty database file
already exists):
$ ./s
In order to create the necessary tables you'll have to run
Blogtiny::Models.create_schema.
The prefered way is define a create-method like this:
def Blogtiny.create
Blogtiny::Models.create_schema
end
All servers or setups using Camping should then call Blogtiny.create on
startup after the app i
Many attempts (3 days now) to get even a single sqlite3 example
running... I've got a little further by creating the database file
from the sqlite3 shell. Now the app connects to an empty db and I get:
ActiveRecord::StatementInvalid SQLite3::SQLException: no such table:
blogtiny_posts: SELE
Weird. I've used sqlite3 on the SQLite which follows with 10.4 earlier.
Could you paste the code you use to connect to the database?
//Magnus Holm
On Mon, May 18, 2009 at 11:22, Dave Everitt wrote:
> Regarding the post below: in case anyone was going to reply about SWIG, I
> checked and found
Regarding the post below: in case anyone was going to reply about
SWIG, I checked and found this on the sqlite3-ruby GIT pages:
"the gem ships with the C source-code pre-built, so (as of version
1.1.1) you no longer need to have SWIG installed."
So my problem is obviously elsewhere... sqlit
11 matches
Mail list logo
