Re: [Cgi-session-user] Trouble with C::S::SQLite

[Mark S. <ma...@su...>]

On Mon, Mar 06, 2006 at 06:28:11PM -0600, Puneet Kishor wrote:
> 
> Rats... exactly the same message as below on Mac OS X 10.3.9 with  
> AciveState Perl 5.8.7 and CGI::Session 4.05 downloaded from CPAN using  
> DBD::SQLite 1.11 (first instance was on a WinXP box). Here is the  
> message --
> 
> [Mon Mar  6 18:23:27 2006] index.cgi: DBD::SQLite::db prepare failed:  
> no such table: sessions(1) at dbdimp.c line 269 at  
> /usr/local/ActivePerl-5.8/lib/site_perl/5.8.7/CGI/Session/Driver/ 
> sqlite.pm line 41 during global destruction.
> [Mon Mar  6 18:23:27 2006] index.cgi: 	(in cleanup) DBD::SQLite::db  
> prepare failed: no such table: sessions(1) at dbdimp.c line 269 at  
> /usr/local/ActivePerl-5.8/lib/site_perl/5.8.7/CGI/Session/Driver/ 
> sqlite.pm line 41 during global destruction.
> [Mon Mar  6 18:23:44 2006] index.cgi: DBD::SQLite::db prepare failed:  
> no such table: sessions(1) at dbdimp.c line 269 at  
> /usr/local/ActivePerl-5.8/lib/site_perl/5.8.7/CGI/Session/Driver/ 
> sqlite.pm line 41 during global destruction.
> [Mon Mar  6 18:23:44 2006] index.cgi: 	(in cleanup) DBD::SQLite::db  
> prepare failed: no such table: sessions(1) at dbdimp.c line 269 at  
> /usr/local/ActivePerl-5.8/lib/site_perl/5.8.7/CGI/Session/Driver/ 
> sqlite.pm line 41 during global destruction.
> 
> This is very frustrating, and I am at my wits end, so any help/guidance  
> from anyone would be very welcome.

Puneet.

Pretend your code is OK and that this a bug in a third party module,
like CGI::Session or DBD::SQLite. 

Write a simple test using Test::More, etc. If it fails, submit a bug
report. If it passes, there's something about the context of your
application making it fail.  

If it passes, keep making changes to the test to make it more like your
application until it fails. The last thing you changed before it starts
to fail must be the bug!

Finally, consider using another driver as a pragmatic solution to keep
the big picture of your project moving. You'll only need to change one
line of code to switch back to the SQLite driver later! 

	Mark