On Wednesday 22 March 2006 9:43 pm, Jim Dodgen wrote:
> for a query like
>
> select * from a join b on a.x = b.z
>
> anyone know how to get all the column names of the fields that would be
> returned from the query?
>
> I am using the DBD::SQLite PERL module
>
This script shows you how to get t
On Monday 10 October 2005 2:32 pm, Cyril Scetbon wrote:
> Scott Leighton wrote:
> >On Monday 10 October 2005 6:03 am, Cyril Scetbon wrote:
> >>No error code is returned cause the script is blocked by the instruction
> >>$dbh->do($req);
> >
> > Change th
On Monday 10 October 2005 6:03 am, Cyril Scetbon wrote:
>
> No error code is returned cause the script is blocked by the instruction
> $dbh->do($req);
>
Change that line to
$dbh->do($req) or die $dbh->errstr;
to get an error displayed.
Scott
--
POPFile, the OpenSource EMail Classi
On Thursday 09 June 2005 7:15 am, Puneet Kishor wrote:
> I've been a reading a lot on the "database locked" problem, but still
> need guidance trying to locate the source of my problem.
>
> environment: DBI/DBD::SQLite (latest versions) with SQLite3 (3.2.1) on
> Mac OS X (10.3.9).
>
> I am trying t
On Saturday 23 April 2005 7:15 pm, steve wrote:
> Assume a database table named Good has a column named "bob".
> The following command will return ALL rows in the table regardless of their
> content:
>
> SELECT * FROM Good WHERE bob LIKE "bob";
>
> Is this by design? If so, is there a workaround f
On Saturday 23 April 2005 7:15 pm, steve wrote:
> Assume a database table named Good has a column named "bob".
> The following command will return ALL rows in the table regardless of their
> content:
>
> SELECT * FROM Good WHERE bob LIKE "bob";
>
> Is this by design? If so, is there a workaround f
On Tuesday 07 December 2004 10:28 am, Jeff Flowers wrote:
> Is it possible to set the .width option when calling the sqlite
> frontend? I was surprised that there wasn't a options to do this,
> something like:
>
> sqlite3 -column -header -width '30 30 5 5' dbname
>
>
You didn't mention your OS, bu
On Thursday 07 October 2004 5:11 pm, Freeman, Michael wrote:
> I put in a ticket, but I thought I'd also throw this question out to you
> guys. I'm having some problems with a script that is using sqlite. I'll
> cut and paste from the ticket:
>
>
>
> POE::Component::EasyDBI Got STDERR from child, w
On Saturday 11 September 2004 4:45 pm, Darren Duncan wrote:
> At 4:05 PM -0700 9/11/04, Scott Leighton wrote:
> > I'm not seeing any such problem here. The following code works
> >perfectly with DBD::SQLite2 v0.33 and DBD::SQLite v1.05.
> >
> > You don't &#
On Saturday 11 September 2004 3:19 pm, Darren Duncan wrote:
> Just now I installed the newest versions of DBD::SQLite v1.05 (3.06)
> and DBD::SQLite2 v0.33 (2.8.15). They both tested and installed with
> no problems, along with DBI v1.43 and Perl v5.8.5, all using GCC 3.3
> on Mac OS X 10.2.8.
>
>
On Sunday 08 August 2004 8:32 pm, Scott Leighton wrote:
>
>Solved! Just to close the loop on this for the benefit of any other
> DBD::SQLite users who may be trying to upgrade from v 0.31 to v 1.x.x.
> Watch out for cases where your former working code left unfinished SELECT
> s
On Sunday 22 August 2004 8:03 pm, Panther wrote:
> When I compile module DBD-SQLite-1.03 as root in slackware 10 with perl
> 5.8.4 I have an error when I write:
Get DBD::SQLite 1.04 from CPAN, it should compile clean. There were
bugs in versions 1.00 - 1.03.
Scott
--
POPFile, the OpenSource
On Saturday 14 August 2004 10:28 am, cai yuan wrote:
> Hi,
> I would like to test the SQLite in some linux embedded system.
> I read the limitation document and it says
> "To change a table you have to delete it (saving its contents to a
> temporary table) and recreate it from scratch." (Stated in
On Sunday 08 August 2004 6:52 pm, Scott Leighton wrote:
> On Sunday 08 August 2004 6:26 pm, D. Richard Hipp wrote:
> > Scott Leighton wrote:
> >
> > Whenever you start a SELECT statement (by calling sqlite3_step()) but
> > have not finalized that statement (
On Sunday 08 August 2004 6:26 pm, D. Richard Hipp wrote:
> Scott Leighton wrote:
>
> Whenever you start a SELECT statement (by calling sqlite3_step()) but have
> not finalized that statement (using sqlite3_finalize() or sqlite3_reset())
> the statement is probably holding a lock
On Sunday 08 August 2004 3:53 pm, Scott Leighton wrote:
> On Sunday 08 August 2004 3:42 pm, D. Richard Hipp wrote:
> > You should start looking for problems. The -journal file should be
> > deleted the moment a transaction commits. In fact, transaction commit is
> > defin
On Sunday 08 August 2004 3:42 pm, D. Richard Hipp wrote:
>
> You should start looking for problems. The -journal file should be deleted
> the moment a transaction commits. In fact, transaction commit is defined
> as the moment when the journal file is deleted. If the journal is never
> deleted,
I have finally succeeded in getting DBD::SQLite v 1.02 compiled and installed
on my AMD64 and have therefore started working with SQLite3. After reading
the documentation about locking and concurrency here
http://www.sqlite.org/lockingv3.html I am left with the impression that the
life of the
On Wednesday 04 August 2004 7:27 am, D. Richard Hipp wrote:
> Detlef Groth wrote:
> > Hello,
> >
> > I could recently compile the sqlite2.x code without problems but now I
> > can't compile the the 3.0.3 branch.
> >
> > The main problem is in:
> > sqliteInt.h:129: parse error before "uptr"
> > sqli
On Monday 26 July 2004 8:14 pm, you wrote:
> I'm trying to compile the latest cvs version of 3.0 on my
> AMD64 system and I'm running into this problem.
>
Well, scratch that, my mistake.
Apparently I screwed up my local copy of CVS. I just blew
it away and refreshed with a clean checkou
I'm trying to compile the latest cvs version of 3.0 on my
AMD64 system and I'm running into this problem.
gcc -g -O2 -DOS_UNIX=1 -DHAVE_USLEEP=1 -I. -I../sqlite/src -DNDEBUG
-c ../sqlite/src/btree.c -fPIC -DPIC -o .libs/btree.o
gcc -g -O2 -DOS_UNIX=1 -DHAVE_USLEEP=1 -I. -I../sqlite/src -D
On Monday 26 July 2004 6:09 pm, Dennis Volodomanov wrote:
> Hello all,
>
> I just downloaded the whole repository and tried to recompile (v3), but
> in sqliteInt.h there's a header include "config.h" and this file is not
> present anywhere :-(
>
> Am I missing something? I was able to compile fine
On Thursday 22 July 2004 8:56 pm, Darren Duncan wrote:
> At 11:22 PM -0400 7/22/04, [EMAIL PROTECTED] wrote:
> >Scott Leighton <[EMAIL PROTECTED]> writes:
> > > OK, but what happens to existing sqlite databases we're already
> >>
> >> using with
On Thursday 22 July 2004 2:40 pm, Darren Duncan wrote:
> Good news. And since Matt hasn't brought it up here yet, I will.
>
> Yesterday, Matt Sergeant posted DBD::SQLite v1.0 on CPAN, which is
> the first version to incorporate SQLite v3.x.
>
> Suffice it to say, you actually can start using SQLit
24 matches
Mail list logo
