-Original Message-
From: Gerard Samuel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 18, 2004 11:41 AM
To: Fred Williams; [EMAIL PROTECTED]
Subject: Re: [sqlite] Select statements returned column names
On Wednesday 18 February 2004 12:19 pm, Fred Williams wrote:
> Just did some tes
Cesare D'Amico <[EMAIL PROTECTED]> writes:
> Alle 21:54, martedà 17 febbraio 2004, Andreas Rottmann ha scritto:
>> Since SQLite
>> DB files are not stored in a central, known place, automatic upgrades
>> (like e.g. the Debian PostgreSQL package does) can not be attempted
>> by the Debian SQLite pa
At 10:27 AM -0800 2/18/04, Andrew Watkins wrote:
Hello,
I'm creating a client application in .Net and I am leaning towards the idea of
keeping the database open for the life of the program as opposed to closing it
after every transaction or group of statements.
What I wanted to know was could the d
Andrew Watkins wrote:
I'm creating a client application in .Net and I am leaning towards the idea of
keeping the database open for the life of the program as opposed to closing it
after every transaction or group of statements.
What I wanted to know was could the database be corrupted if the progra
Hello,
I'm creating a client application in .Net and I am leaning towards the idea of
keeping the database open for the life of the program as opposed to closing it
after every transaction or group of statements.
What I wanted to know was could the database be corrupted if the program was
shutdow
Alle 21:54, martedì 17 febbraio 2004, Andreas Rottmann ha scritto:
> Since SQLite
> DB files are not stored in a central, known place, automatic upgrades
> (like e.g. the Debian PostgreSQL package does) can not be attempted
> by the Debian SQLite package that will ship with Sarge.
Debian (which I
On Wednesday 18 February 2004 12:34 pm, Ilia Alshanetsky wrote:
> The old PHP interface did strchr() on the column names in order to 'strip'
> the any data (table name) before the column name. This is rather
> inefficient and should not be done and thus was removed.
Thanks for your reply. I would
On Wednesday 18 February 2004 12:19 pm, Fred Williams wrote:
> Just did some testing on the "other" databases I have available. This
> "feature" of SQLite does seem to be unique. I am early in the learning
> curve on SQLite, and had not found this particular "enhancement" as yet.
> Nice to know,
I wasn't exactly sure of how to classify this to enter it as an official
bug. Also I using a combination of software that I am certain is out of the
ordinary. First I'll discuss the assertion, then my environment.
What I am seeing is the following message:
assertion "!pPager->noSync" fa
Just did some testing on the "other" databases I have available. This
"feature" of SQLite does seem to be unique. I am early in the learning
curve on SQLite, and had not found this particular "enhancement" as yet.
Nice to know, and avoid!
Looks like to me it is time for a new PRAGMA!
I am not w
On Wednesday 18 February 2004 11:23 am, Gerard Samuel wrote:
> On Wednesday 18 February 2004 10:58 am, Ilia Alshanetsky wrote:
> > Yes, this is the correct behavior, without the table 'prefix' if you have
> > common column names in the result set the data would lost.
>
> True about common column na
On Wednesday 18 February 2004 10:58 am, Ilia Alshanetsky wrote:
> Yes, this is the correct behavior, without the table 'prefix' if you have
> common column names in the result set the data would lost.
>
True about common column names. But isn't that where aliases come in???
E.g. select a.foo as
Im currently interfacing with sqlite via php 4.3.5-RC2.
The latest version of sqlite, distributed by php snaps
(http://snaps.php.net/win32/PECL_STABLE/) is 2.8.11.
Im currently experiencing behaviour with sqlite that I didn't experience when
I was using version 2.8.3 several months ago.
If I have
Hi,
again I've figured out an inconsistency with subselects (and again I think it's
sqlite's fault... ;)
SQLite version 2.8.12
Enter ".help" for instructions
sqlite> .echo on
sqlite> .read test.sql
.read test.sql
DROP VIEW t1view;
DROP VIEW t1view2;
DROP TABLE t1;
CREATE TABLE t1 (
id
Hi,
i've a problem with linebreaks in sqlite.
my mysqldump has some \n for linebreaks, but sqlite do not undestand this.
how can i escape the linebreak?
THX
Sascha Wojewsky
> From: Darren Duncan
> At 3:16 PM +0100 2/17/04, zeb warrior wrote:
> >I've enjoyed this group very much but it's time for me to
> leave. I've
> >sent an email to sqlite-user-help and got the information to
> unsub, but
> >alas no luck. While the system did ask me to confirm the
> unsub lette
16 matches
Mail list logo
