Re: [sqlite] pragmas in subselects?

[Petite Abeille]

On Jan 29, 2014, at 9:58 PM, big stone  wrote:

> (killing two birds with one stone)

No. One bird only.

Enhancing ‘alter table’ is another kettle of fish altogether.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] pragmas in subselects?

[big stone]

Would the implementation of a subset of  "Information schema" also allow
the "Alter table" function to work in more (SQL) standard situations ?

(killing two birds with one stone)

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] pragmas in subselects?

[Stephan Beal]

On Sun, Jan 26, 2014 at 9:45 PM, Jay Kreibich  wrote:

>
> Chapter 10 of Using SQLite covers virtual tables.  One of the examples
> given shows how to wrap a PRAGMA statement, so it can be used as system
> catalog and used in normal SELECT statements.  It would be pretty easy to
> expand the given example to cover almost any SQL statement (including any
> PRAGMA).
>
> Even if you don't have a copy of the book, you can download the example
> code off the product page:
>

i've got the book, so many thanks for that tip - i'll take a look.

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] pragmas in subselects?

[Clemens Ladisch]

big stone wrote:
> There is a non-logicality of having "pragma table_info(my_table)" :
> - answering like a select,
> - but being not usable as a "select", nor queriable by a "select".

SQLite's PRAGMA implementations do not plug into the internal query
mechanism used by SELECT, but hardcode a VDBE program that directly
generates the output as seen by sqlite3_step/column_xxx.  There is no
built-in mechanism that would allow to use the output of a VDBE program
directly as input for other queries.  (But it is possible to write
a virtual table that does this.)


Regards,
Clemens
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] pragmas in subselects?

[Simon Slavin]

On 26 Jan 2014, at 10:32pm, Petite Abeille  wrote:

> What SQLite would really benefit from is a proper, consistent, queryable data 
> dictionary such as the the standard information schema:
> 
> http://en.wikipedia.org/wiki/Information_schema

I would like that for in SQLite4.  Something close to SQL-92 without messing up 
the tenets of SQLite.  For those interested, it's section 21 page 533 of



but that's a horrible description and very hard to understand.  It if turns out 
to be useful for the SQLite community I can update an simple one with examples 
I've got lying about somewhere.

Simon.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] pragmas in subselects?

[Petite Abeille]

On Jan 26, 2014, at 11:19 PM, big stone  wrote:

> ==> Is it the reason ?

Well, that pragmas are not directly queryable from SQL just add insult to 
injury. 

What SQLite would really benefit from is a proper, consistent, queryable data 
dictionary such as the the standard information schema:

http://en.wikipedia.org/wiki/Information_schema
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] pragmas in subselects?

[big stone]

There is a non-logicality of having "pragma table_info(my_table)" :
- answering like a select,
- but being not usable as a "select", nor queriable by a "select".

Other databases seem more logical on this practical matter.

Multi-motor tools, like dbeaver, have currently much less good support of
"database diagram" when dealing with SQLite.
==> Is it the reason ?
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] pragmas in subselects?

[Jay Kreibich]

Chapter 10 of Using SQLite covers virtual tables.  One of the examples given 
shows how to wrap a PRAGMA statement, so it can be used as system catalog and 
used in normal SELECT statements.  It would be pretty easy to expand the given 
example to cover almost any SQL statement (including any PRAGMA).

Even if you don't have a copy of the book, you can download the example code 
off the product page:
http://shop.oreilly.com/product/9780596521196.do
The example code download link is on the right side of the page.

Somewhere I've got a virtual table that will wrap any SQL statement, but I'm 
not sure where it is.  Just modify the book's example code to take an SQL 
statement as a table creation parameter and you should be able to create 
something similar.

 -j


On Jan 26, 2014, at 11:01 AM, Petite Abeille  wrote:

> 
> On Jan 26, 2014, at 5:09 PM, Stephan Beal  wrote:
> 
>> Is this possible?
> 
> Sadly, no. Much of a PITA.
> 
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

--  
Jay A. Kreibich < J A Y  @  K R E I B I.C H >

"Intelligence is like underwear: it is important that you have it, but showing 
it to the wrong people has the tendency to make them feel uncomfortable." -- 
Angela Johnson




___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] pragmas in subselects?

[Luuk]

On 26-01-2014 17:09, Stephan Beal wrote:

Hi, all,

is there a syntactical construct which will allow me to use a pragma in a
subselect? e.g. i'm trying to do...

sqlite> pragma table_info(vfile);
cid|name|type|notnull|dflt_value|pk
0|id|INTEGER|0||1
1|vid|INTEGER|0||0
...

sqlite> select name from (pragma table_info(vfile));
Error: near "(": syntax error
sqlite> select name from pragma table_info(vfile);
Error: near "(": syntax error
sqlite> create view v as pragma table_info(vfile);
Error: near "pragma": syntax error
sqlite> create view v as select (pragma table_info(vfile));
Error: near "table_info": syntax error
sqlite> create view v as select pragma table_info(vfile);
Error: near "(": syntax error

Is this possible?




http://stackoverflow.com/questions/685206/sqlite-how-to-get-a-list-of-column-names

answer: not in SQLite
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] pragmas in subselects?

[Petite Abeille]

On Jan 26, 2014, at 5:09 PM, Stephan Beal  wrote:

> Is this possible?

Sadly, no. Much of a PITA.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Pragmas

[Richard Hipp]

On Thu, Jan 16, 2014 at 2:02 PM, Tim Streater  wrote:

> From time to time I see the use of a particular pragma recommended by the
> experts here. However, the introduction to:
>
> http://www.sqlite.org/pragma.html
>
> specifically warns that any pragma is at risk of being removed from one
> release to the next. And indeed, some are marked as deprecated. It seems to
> me as a user that I'm getting mixed messages here. I'd appreciate knowing
> what the actual policy is.
>

I need to change the documentation.

There are so many hundreds of thousands of applications using SQLite, that
I can't change any of the pragma (even the deprecated ones) without
creating a ruckus.  So you can pretty much count on them being there.


>
> Thanks.
>
>
>
> --
> Cheers  --  Tim
>
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
>


-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Pragmas for in-memory databases

[Jay A. Kreibich]

On Sat, Apr 17, 2010 at 05:27:35PM -0700, andrew fabbro scratched on the wall:
> If a DB is entirely in-memory (i.e., opened with :memory:), which pragmas
> can be used to improve performance?
> 
> (1) I assume synchronous = OFF is desirable

  N/A.  There is no such thing as synchronizing memory writes.

> (2) I'm guessing journal_mode = MEMORY is already set.

  No need to guess. Docs: 
"Note that the journal_mode for an in-memory database is either
 MEMORY or OFF and can not be changed to a different value."

> Is journal_mode = OFF another possible speed gain?  Of course, then
> one loses the ability to do transactions.

  If it is, it is likely to be very minor.

> (3) If journaling is set to MEMORY, what is the best setting then for
> journal_size_limit?

  N/A.  Only applies to on-disk journals.

> I guess it depends on how much memory one is willing to
> use overall, but in this case, it's not there for crash protection but
> rather to support transactions.  Is there a sizing guide?

  JOURNAL_SIZE_LIMIT doesn't limit the size of an active journal, only
  left-over journals.

  Docs:
"This pragma may be used to limit the size of journal files left in
the file-system **after** transactions are committed..."  [emp. added]

> (4) How about locking_mode?  I imagine it would be OK and a small gain to
> set to NORMAL in a single-threaded application, but obviously not a good
> idea for multi-threaded.

  Docs:
"The "temp" database (in which TEMP tables and indices are stored)
and in-memory databases always uses exclusive locking mode."

  Multi-threaded has nothing to do with it.  Even with multi-thread you
  still have to sync your use of the database connection.

> (5) If referential integrity can be sacrificed (the Oracle DBA in my
> whimpers a little), foreign_keys = false, but that's true whether on-disk or
> in-memory.

  Yes.  But if you don't have FKs, it is unlikely to make much difference.

> (6) Is there any advantage to playing with:
>- page_size?

  Doubt it.  Unless you're storing a lot of TEXT/BLOB values that are
  just slightly larger than a page, and getting a lot of fragmentation,
  there isn't likely to be much difference.

  If you're memory bound a slightly larger page is likely to help, but
  that's a big balancing act that depends a lot on the data and layout
  of the database.

>- default_cache_size?

  N/A.  This only comes into play when a database is re-opened.  You
  can't do that with an instance of an in-memory DB.

>- read_uncommitted?  I assume there's a different answer for single- vs.
> multi-threaded (or rather, depending on how readers/writers interact)

  N/A.  This only applies to shared-cache mode.  Shared cache mode only
  applies when you have multiple connections to the same database.  You
  can't have multiple connections to an in-memory instance.


   -j

-- 
Jay A. Kreibich < J A Y  @  K R E I B I.C H >

"Our opponent is an alien starship packed with atomic bombs.  We have
 a protractor."   "I'll go home and see if I can scrounge up a ruler
 and a piece of string."  --from Anathem by Neal Stephenson
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

RE: [sqlite] Pragmas

[Manzoor Ilahi Tamimy]

Dear Anish

I am using the same
---
 sqlite3_open(database, &db);
 sqlite3_exec(db, "PRAGMA page_size=4096", NULL, NULL, NULL);
sqlite3_exec(db, "create table t...
---

and its working the only file included is (#include "sqlite3.h")

regards,

TAMIMY


- Original Message - 
From: "Anish Enos Mathew" <[EMAIL PROTECTED]>
To: 
Sent: Monday, May 22, 2006 3:49 PM
Subject: RE: [sqlite] Pragmas


>
> Hi,
>   I used the following command for setting the page size.
>
>   PRAGMA page_size = 4096; before the table is created.
>
> But it is showing an error, "PRAGMA undeclared". What could be the
> problem? Do I need to include any header file for it?
>
> -Original Message-
> From: Nemanja Corlija [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 22, 2006 1:12 AM
> To: sqlite-users@sqlite.org; [EMAIL PROTECTED]
> Subject: Re: [sqlite] Pragmas
>
> On 5/21/06, Unit 5 <[EMAIL PROTECTED]> wrote:
>> I am a bit confused on how to change the page_size
>> using the pragma command.  The documentation says:
>>
>> "The page-size may only be set if the database has not
>> yet been created."
>
> The database is created when you create first table in it. Run the
> pragma before your first CREATE TABLE query.

RE: [sqlite] Pragmas

[Anish Enos Mathew]

Hi,
   I used the following command for setting the page size.

   PRAGMA page_size = 4096; before the table is created.

But it is showing an error, "PRAGMA undeclared". What could be the
problem? Do I need to include any header file for it?

-Original Message-
From: Nemanja Corlija [mailto:[EMAIL PROTECTED]
Sent: Monday, May 22, 2006 1:12 AM
To: sqlite-users@sqlite.org; [EMAIL PROTECTED]
Subject: Re: [sqlite] Pragmas

On 5/21/06, Unit 5 <[EMAIL PROTECTED]> wrote:
> I am a bit confused on how to change the page_size
> using the pragma command.  The documentation says:
>
> "The page-size may only be set if the database has not
> yet been created."

The database is created when you create first table in it. Run the
pragma before your first CREATE TABLE query.

--
Nemanja Corlija <[EMAIL PROTECTED]>


The information contained in, or attached to, this e-mail, contains 
confidential information and is intended solely for the use of the individual 
or entity to whom they are addressed and is subject to legal privilege. If you 
have received this e-mail in error you should notify the sender immediately by 
reply e-mail, delete the message from your system and notify your system 
manager. Please do not copy it for any purpose, or disclose its contents to any 
other person. The views or opinions presented in this e-mail are solely those 
of the author and do not necessarily represent those of the company. The 
recipient should check this e-mail and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused, directly or 
indirectly, by any virus transmitted in this email.

www.aztecsoft.com

Re: [sqlite] Pragmas

[Nemanja Corlija]

On 5/21/06, Unit 5 <[EMAIL PROTECTED]> wrote:

I am a bit confused on how to change the page_size
using the pragma command.  The documentation says:

"The page-size may only be set if the database has not
yet been created."


The database is created when you create first table in it. Run the
pragma before your first CREATE TABLE query.

--
Nemanja Corlija <[EMAIL PROTECTED]>

Re: [sqlite] Pragmas

[Dennis Cote]

Drew, Stephen wrote:
I would be grateful if somebody who has
experience using these column name pragmas could take a look and see if
either:
(a) This documentation is incorrect:
http://www.sqlite.org/cvstrac/wiki?p=ColumnNames
(b) I am not using SQLite correctly.
 

Steve,
I have tried these pragmas in the past, and I also found that they 
didn't work as advertised.

The following trace from a fresh build of SQLite using the latest CVS 
source shows that the full_column_names pragma doesn't produce full 
column names as documented.

SQLite version 3.2.1
Enter ".help" for instructions
sqlite> .echo on
sqlite> .read "c:\\temp\\col_prag.sql"
.read "c:\\temp\\col_prag.sql"
drop table test1;
SQL error: no such table: test1
drop table test2;
SQL error: no such table: test2
create table test1 (id integer primary key, data1 varchar);
create table test2 (id integer, data2 varchar);
insert into test1 values(1, 'a');
insert into test1 values(2, 'b');
insert into test2 values(1, 'A');
insert into test2 values(2, 'B');
pragma short_column_names;
1
pragma full_column_names;
0
pragma short_column_names=off;
pragma full_column_names=on;
pragma short_column_names;
0
pragma full_column_names;
1
.header on
select * from test1, test2 where test1.id=test2.id;
id|data1|id|data2
1|a|1|A
2|b|2|B
select * from test1 as T1, test2 as T2 where T1.id=T2.id;
id|data1|id|data2
1|a|1|A
2|b|2|B
select test1.*, test2.* from test1, test2 where test1.id=test2.id;
id|data1|id|data2
1|a|1|A
2|b|2|B
select T1.*, T2.* from test1 as T1, test2 as T2 where T1.id=T2.id;
id|data1|id|data2
1|a|1|A
2|b|2|B
select T1.id, data2 from test1 as T1 join test2 as T2 using(id);
test1.id|test2.data2
1|A
2|B
select T1.id, data2 from test1 as T1 join test2 as T2 on T1.id=T2.id;
test1.id|test2.data2
1|A
2|B
Clearly these results do not agree with the documentation for this case 
(copied below).

   *Case 5: short_column_names=OFF and full_column_names=ON*
   If cases 1 and 2 do not apply and short_column_names=OFF and
   full_column_names=ON then the result set column name is constructed
   as "TABLE.COLUMN" where TABLE is the name of the table from which
   the data is taken and COLUMN is the name of the column within TABLE
   from which the data was taken. If the table is aliased by the use of
   an AS clause in the FROM expression then the alias is used instead
   of the original table name.
First, the implicit joins in the first 4 selects are ignored. Secondly, 
the explicit joins in the last two selects are returning the original 
table name rather than the table's alias name.

You aren't doing anything wrong, SQLite is.
Dennis Cote

RE: [sqlite] Pragmas

[Drew, Stephen]

Attachment included:


#include "sqlite3.h"
#include 
#include 
#include 
#include 

#define CHECK_CODE(db, rc, msg) \
if (rc!=SQLITE_OK)  \
{ do_exit(db, rc, msg); }   

char* test_pragmas[][2] = { { "PRAGMA short_column_names=OFF;", "PRAGMA
full_column_names=OFF;" }
  , { "PRAGMA
short_column_names=ON;", "PRAGMA full_column_names=OFF;" }
  , { "PRAGMA
short_column_names=OFF;", "PRAGMA full_column_names=ON;" }
};

void do_exit(sqlite3* db, int rc, char* msg=NULL)
{
printf("Exiting with error code %d\n", rc);
if (msg)
printf("%s\n", msg);
if (db)
printf("%s\n", sqlite3_errmsg(db));
exit(0);
}

void execute(sqlite3* db, char* sql)
{
char* zErrMsg=NULL;
int rc = sqlite3_exec(db, sql, 0, 0, &zErrMsg);
CHECK_CODE(db, rc, zErrMsg);
}

void query(sqlite3* db, char* sql)
{
const char* zTail=NULL;
sqlite3_stmt*   vm=NULL;
int rc=sqlite3_prepare(db, sql, (int) strlen(sql), &vm, &zTail);
CHECK_CODE(db, rc, "Error preparing SQL query");
if (vm==NULL)
CHECK_CODE(db, 1, "Error prerparing SQL query 2");

int col_qty = sqlite3_column_count(vm);

// TODO: add data type and flags
for (int i=0; ihttp://www.sqlite.org/cvstrac/wiki?p=ColumnNames

(b) I am not using SQLite correctly.

Here are my results:

CREATE TABLE TEST1 (id NUMERIC, data VARCHAR2); CREATE TABLE TEST2 (id
NUMERIC, data2 VARCHAR2);

Query = "SELECT T1.*, T2.* FROM TEST1 T1, TEST2 T2 WHERE T1.id = T2.id;"

Short=OFF, Full=OFF
Column 0: id
Column 1: data
Column 2: id
Column 3: data2
This should be the same as the third scenario, as my query is a join
involving two tables.

Short=ON, Full=OFF (default, but set anyway) Column 0: id Column 1: data
Column 2: id Column 3: data2 This is as expected from the docs.

Short=OFF, Full=ON
Column 0: id- should be T1.id
Column 1: data  - should be T1.data
Column 2: id- should be T2.id
Column 3: data2 - should be T2.data2
This is wrong, according to the documentation. These strike me as more
of what I would expect had I run the query: SELECT * FROM TEST1 T1,
TEST2 T2 WHERE T1.id=T2.id.

These clearly do not match the documentation. Also, the documentation
example does not provide the core comparison case of a query joining two
or more tables.

I would really appreciate help on this if anyone can spare the time. I
need to either move to SQLite 3 or find an alternative.  I cannot move
to SQLite 3 if I cannot replicate the behaviour of SQLite 2, even with
pragmas.

Many thanks,
Steve



-Original Message-
From: Drew, Stephen
Sent: 03 May 2005 15:49
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] Pragmas

Understood.

I fall into case 5, and this is definitely not the way they're
represented. So assuming my code was correct, and the documentation
refers to 3.2.1, the documentation is STILL incorrect?

Regards,
Steve 

-----Original Message-
From: D. Richard Hipp [mailto:[EMAIL PROTECTED]
Sent: 03 May 2005 15:26
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Pragmas

On Tue, 2005-05-03 at 15:09 +0100, Drew, Stephen wrote:
> This is not the case for the version of SQLite 3.2.1 I am using.   Is
> the documentation incorrect, or am I doing anything wrong?
>

Documentation is wrong.  See http://www.sqlite.org/cvstrac/wiki?
p=ColumnNames
--
D. Richard Hipp <[EMAIL PROTECTED]>

RE: [sqlite] Pragmas

[Drew, Stephen]

Hello,

I have included a C++ file which will compile against SQLite 3.2.1 under
Visual C++ 7 in Windows (it is almost C, and only has one Win32 Api call
- to sleep at the end).  I would be grateful if somebody who has
experience using these column name pragmas could take a look and see if
either:

(a) This documentation is incorrect:
http://www.sqlite.org/cvstrac/wiki?p=ColumnNames

(b) I am not using SQLite correctly.

Here are my results:

CREATE TABLE TEST1 (id NUMERIC, data VARCHAR2);
CREATE TABLE TEST2 (id NUMERIC, data2 VARCHAR2);

Query = "SELECT T1.*, T2.* FROM TEST1 T1, TEST2 T2 WHERE T1.id = T2.id;"

Short=OFF, Full=OFF
Column 0: id
Column 1: data
Column 2: id
Column 3: data2
This should be the same as the third scenario, as my query is a join
involving two tables.

Short=ON, Full=OFF (default, but set anyway)
Column 0: id
Column 1: data
Column 2: id
Column 3: data2
This is as expected from the docs.

Short=OFF, Full=ON
Column 0: id- should be T1.id
Column 1: data  - should be T1.data
Column 2: id- should be T2.id
Column 3: data2 - should be T2.data2
This is wrong, according to the documentation. These strike me as more
of what I would expect had I run the query: SELECT * FROM TEST1 T1,
TEST2 T2 WHERE T1.id=T2.id.

These clearly do not match the documentation. Also, the documentation
example does not provide the core comparison case of a query joining two
or more tables.

I would really appreciate help on this if anyone can spare the time. I
need to either move to SQLite 3 or find an alternative.  I cannot move
to SQLite 3 if I cannot replicate the behaviour of SQLite 2, even with
pragmas.

Many thanks,
Steve



-Original Message-
From: Drew, Stephen 
Sent: 03 May 2005 15:49
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] Pragmas

Understood.

I fall into case 5, and this is definitely not the way they're
represented. So assuming my code was correct, and the documentation
refers to 3.2.1, the documentation is STILL incorrect?

Regards,
Steve 

-Original Message-
From: D. Richard Hipp [mailto:[EMAIL PROTECTED]
Sent: 03 May 2005 15:26
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Pragmas

On Tue, 2005-05-03 at 15:09 +0100, Drew, Stephen wrote:
> This is not the case for the version of SQLite 3.2.1 I am using.   Is
> the documentation incorrect, or am I doing anything wrong?
>

Documentation is wrong.  See http://www.sqlite.org/cvstrac/wiki?
p=ColumnNames
--
D. Richard Hipp <[EMAIL PROTECTED]>

RE: [sqlite] Pragmas

[Drew, Stephen]

Understood.

I fall into case 5, and this is definitely not the way they're
represented. So assuming my code was correct, and the documentation
refers to 3.2.1, the documentation is STILL incorrect?

Regards,
Steve 

-Original Message-
From: D. Richard Hipp [mailto:[EMAIL PROTECTED] 
Sent: 03 May 2005 15:26
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Pragmas

On Tue, 2005-05-03 at 15:09 +0100, Drew, Stephen wrote:
> This is not the case for the version of SQLite 3.2.1 I am using.   Is
> the documentation incorrect, or am I doing anything wrong?
>

Documentation is wrong.  See http://www.sqlite.org/cvstrac/wiki?
p=ColumnNames
--
D. Richard Hipp <[EMAIL PROTECTED]>

Re: [sqlite] Pragmas

[D. Richard Hipp]

On Tue, 2005-05-03 at 15:09 +0100, Drew, Stephen wrote:
> This is not the case for the version of SQLite 3.2.1 I am using.   Is
> the documentation incorrect, or am I doing anything wrong?
>

Documentation is wrong.  See http://www.sqlite.org/cvstrac/wiki?
p=ColumnNames
-- 
D. Richard Hipp <[EMAIL PROTECTED]>