sqlite 'ownership' problems

[Jean-Paul Calderone]

On 3 Sep 2006 14:38:51 -0700, rdrink <rdrink at artic.edu> wrote:
>I will try to keep this as suscinct as possible as it might be an
>obvious Q.....
>I am just getting into Py/sqlite (with a fair amount of PHP/MySQL
>background), and am posting this as much for the other noobs as
>myself....
>I started learning sqlite by tinkered around at the command line:
>creating db's, tables, populating them. etc. All fine.
>Then I moved to Python.. and immediately noticed that for a db I had
>created at the cmnd-line, e.g. 'test.db' with a table 'foo', I would
>get the error "_sqlite.DatabaseError: no such table: foo". My suspition
>was that this is a "feature" of sqlite ('flat file' vs. a dynamic db in
>MySQL) where sqlite is 'sensetive' to who creates it... Which seems to
>be borne out by that fact that I have since written one Py script (in
>IDLE) which creates and populates a db, and another that can retrieve
>the data. But...

Just make sure everyone who should be able to read and write the database
has read and write permissions on the database file.  Nothing more is
necessary.

Jean-Paul