[sqlite] Comments in VDBE program

[Sairam Gaddam]

Thanks! Comments are enabled now.

On Thu, Apr 16, 2015 at 4:41 PM, Richard Hipp  wrote:

> On 4/16/15, Sairam Gaddam  wrote:
> > I am using C SQLite interface. How to enable comments in the VDBE program
> > here?
> > because they are not enabled by default.
> > gcc -DSQLITE -DEBUG filename.c ../sqlite3.c -ldl -lpthread
> > I tried with the above line in the terminal but could not succeed in
> > enabling the comments. Can any one help me with this?
> > I am using Linux 64 bit machine.
>
> Add -DSQLITE_ENABLE_EXPLAIN_COMMENTS to the compiler command-line.
>
> > ___
> > sqlite-users mailing list
> > sqlite-users at mailinglists.sqlite.org
> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> >
>
>
> --
> D. Richard Hipp
> drh at sqlite.org
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

[sqlite] Comments in VDBE program

[Sairam Gaddam]

I am using C SQLite interface. How to enable comments in the VDBE program
here?
because they are not enabled by default.
gcc -DSQLITE -DEBUG filename.c ../sqlite3.c -ldl -lpthread
I tried with the above line in the terminal but could not succeed in
enabling the comments. Can any one help me with this?
I am using Linux 64 bit machine.

[sqlite] Comments in VDBE program

[Richard Hipp]

On 4/16/15, Sairam Gaddam  wrote:
> I am using C SQLite interface. How to enable comments in the VDBE program
> here?
> because they are not enabled by default.
> gcc -DSQLITE -DEBUG filename.c ../sqlite3.c -ldl -lpthread
> I tried with the above line in the terminal but could not succeed in
> enabling the comments. Can any one help me with this?
> I am using Linux 64 bit machine.

Add -DSQLITE_ENABLE_EXPLAIN_COMMENTS to the compiler command-line.

> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>


-- 
D. Richard Hipp
drh at sqlite.org

Re: [sqlite] Comments loss in sqlite_master table

[Domingo Alvarez Duarte]

The parallel usage would be a bonus if sqlite with threads could in the
future be instructed to use more available cores on the system.


On Thu, May 29, 2014 at 10:46 AM, big stone  wrote:

> Hi Domingo,
>
> Oracle is doing also this sort of things with there / * parallel */ comment
> keyword.
>
> For example  :
>
> http://docs.oracle.com/cd/E11882_01/server.112/e25523/parallel002.htm#i1006328
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Comments loss in sqlite_master table

[big stone]

Hi Domingo,

Oracle is doing also this sort of things with there / * parallel */ comment
keyword.

For example  :
http://docs.oracle.com/cd/E11882_01/server.112/e25523/parallel002.htm#i1006328
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Comments loss in sqlite_master table

[big stone]

Hi Dan,

You're right : situation is much better than what I thought.
I ddid a more complete check, switching from sqlite.exe 3.8.3  to
sqlite.dll  3.8.4.3

create /*this */
-- really
table /* is */ toty(
-- for
/* truly */
   x --educative
) /*purpose */
-- and comment hunting
 ;

select sql from sqlite_master

... gives back (changing from sqlite.exe  to sqlite.dll and switching to
3.8.4.3) :
CREATE TABLE toty(
-- for
/* truly */
   x --educative
)

So  :
- the loss of header and tail comments doesn't sound logical,
- but it's much better than the total loss I thought.


A small change in favor of head and tail comments preservation would still
be nice, though.

Regards,





So we miss the early and end comments
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Comments loss in sqlite_master table

[Domingo Alvarez Duarte]

Here is a link to a document describing the "COMMENT" syntax
http://docs.oracle.com/cd/B12037_01/server.101/b10759/statements_4009.htm#i2119719


On Thu, May 29, 2014 at 10:34 AM, Domingo Alvarez Duarte  wrote:

> Hello all !
>
> Now that we are talking about comments in sql statements why not extend
> sqlite to accept the "COMMENTS" keyword for fields and tables and then we
> will have a standard way to store extra information about our sql schema.
>
> Cheers !
>
>
> On Thu, May 29, 2014 at 10:10 AM, Luuk  wrote:
>
>> On 29-5-2014 11:00, Dan Kennedy wrote:
>>
>>> On 05/29/2014 03:42 PM, big stone wrote:
>>>
 Hello,

 I miss the functionnality of some other sql motors that keep the
 comments
 inside an object definition, like a table.

>>>
>> 
>>
>>
>>  This sounds quite illogical, as :
 -  Newlines and spaces are kept, (if not around a comment)
 -  the SQLite internal parser would re-parse (and remove comments)
 from the
 original statement without issue.

>>>
>>> I think in practice the text that appears before the first "(" character
>>> in the CREATE TABLE statement is replaced by "CREATE TABLE ".
>>>
>>
>>
>> Before the first "("  ???
>>
>> C:\temp>sqlite3
>> SQLite version 3.8.4.3 2014-04-03 16:53:12
>> Enter ".help" for usage hints.
>> Connected to a transient in-memory database.
>> Use ".open FILENAME" to reopen on a persistent database.
>> sqlite> create /* test */ table test(x);
>> sqlite>
>> sqlite> select * from test;
>> sqlite> .schema
>> CREATE TABLE test(x);
>> sqlite> select sql from sqlite_master;
>> CREATE TABLE test(x)
>> sqlite>
>>
>>
>>
>>
>> ___
>> sqlite-users mailing list
>> sqlite-users@sqlite.org
>> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>>
>
>
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Comments loss in sqlite_master table

[Domingo Alvarez Duarte]

Hello all !

Now that we are talking about comments in sql statements why not extend
sqlite to accept the "COMMENTS" keyword for fields and tables and then we
will have a standard way to store extra information about our sql schema.

Cheers !


On Thu, May 29, 2014 at 10:10 AM, Luuk  wrote:

> On 29-5-2014 11:00, Dan Kennedy wrote:
>
>> On 05/29/2014 03:42 PM, big stone wrote:
>>
>>> Hello,
>>>
>>> I miss the functionnality of some other sql motors that keep the comments
>>> inside an object definition, like a table.
>>>
>>
> 
>
>
>  This sounds quite illogical, as :
>>> -  Newlines and spaces are kept, (if not around a comment)
>>> -  the SQLite internal parser would re-parse (and remove comments)
>>> from the
>>> original statement without issue.
>>>
>>
>> I think in practice the text that appears before the first "(" character
>> in the CREATE TABLE statement is replaced by "CREATE TABLE ".
>>
>
>
> Before the first "("  ???
>
> C:\temp>sqlite3
> SQLite version 3.8.4.3 2014-04-03 16:53:12
> Enter ".help" for usage hints.
> Connected to a transient in-memory database.
> Use ".open FILENAME" to reopen on a persistent database.
> sqlite> create /* test */ table test(x);
> sqlite>
> sqlite> select * from test;
> sqlite> .schema
> CREATE TABLE test(x);
> sqlite> select sql from sqlite_master;
> CREATE TABLE test(x)
> sqlite>
>
>
>
>
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Comments loss in sqlite_master table

[Luuk]

On 29-5-2014 11:00, Dan Kennedy wrote:

On 05/29/2014 03:42 PM, big stone wrote:

Hello,

I miss the functionnality of some other sql motors that keep the comments
inside an object definition, like a table.





This sounds quite illogical, as :
-  Newlines and spaces are kept, (if not around a comment)
-  the SQLite internal parser would re-parse (and remove comments)
from the
original statement without issue.


I think in practice the text that appears before the first "(" character
in the CREATE TABLE statement is replaced by "CREATE TABLE ".



Before the first "("  ???

C:\temp>sqlite3
SQLite version 3.8.4.3 2014-04-03 16:53:12
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> create /* test */ table test(x);
sqlite>
sqlite> select * from test;
sqlite> .schema
CREATE TABLE test(x);
sqlite> select sql from sqlite_master;
CREATE TABLE test(x)
sqlite>



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

Re: [sqlite] Comments loss in sqlite_master table

[Dan Kennedy]

On 05/29/2014 03:42 PM, big stone wrote:

Hello,

I miss the functionnality of some other sql motors that keep the comments
inside an object definition, like a table.

Example : (with sqlite.exe 3.8.3)

create table /* This table has an educative purpose */ toto(x);
create table /* This table has an educative purpose */
toty(x  );
create table
 totz(x  );
select sql from sqlite_master;

... gives :
CREATE TABLE TOTO(X)
CREATE TABLE TOTY(X  )
CREATE TABLE
TOTZ(X)

... instead of the original  full statements :
create table /* This table has an educative purpose */ toto(x)
create table /* This table has an educative purpose */
toty(x  )
create table
 totz(x  )


This sounds quite illogical, as :
-  Newlines and spaces are kept, (if not around a comment)
-  the SQLite internal parser would re-parse (and remove comments) from the
original statement without issue.


I think in practice the text that appears before the first "(" character 
in the CREATE TABLE statement is replaced by "CREATE TABLE ". 
This is because if the user enters "CREATE TABLE main." we 
don't want to store "main." in the sqlite_master file. So I'd say if the 
comment appears inside the parenthesis it will probably be preserved.


Of course, even if that is correct, it's just an artifact of the 
implementation, not part of a published interface that one would expect 
not to change in future versions.


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

Re: [sqlite] Comments loss in sqlite_master table

[Stephan Beal]

On Thu, May 29, 2014 at 10:48 AM, Luuk  wrote:

> According to this:
> http://www.sqlite.org/lang_createtable.html
>
> The comment is not part of the 'full statement'.


According to the grammar charts, comments can't appear at all. Comments
being allowed to appear is implicit.

That said: there are very likely client programs out there which parse the
schema from sqlite_master for various purposes, and comments could very
well break them:

create table foo(a)
-- old version: create table foo(a,b)
;


-- 
- 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] Comments loss in sqlite_master table

[big stone]

Hi Luuk,

You're right : there is also a problem of consistency with documentation .

Neither the spaces around 'x' in  'toty(   x )' are in the
documentation,but SQLite kept those useless spaces anyway.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Comments loss in sqlite_master table

[Luuk]

On 29-5-2014 10:42, big stone wrote:

Hello,

I miss the functionnality of some other sql motors that keep the comments
inside an object definition, like a table.

Example : (with sqlite.exe 3.8.3)

create table /* This table has an educative purpose */ toto(x);
create table /* This table has an educative purpose */
toty(x  );
create table
 totz(x  );
select sql from sqlite_master;

... gives :
CREATE TABLE TOTO(X)
CREATE TABLE TOTY(X  )
CREATE TABLE
TOTZ(X)

... instead of the original  full statements :
create table /* This table has an educative purpose */ toto(x)
create table /* This table has an educative purpose */
toty(x  )


According to this:
http://www.sqlite.org/lang_createtable.html

The comment is not part of the 'full statement'.

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

[sqlite] Comments loss in sqlite_master table

[big stone]

Hello,

I miss the functionnality of some other sql motors that keep the comments
inside an object definition, like a table.

Example : (with sqlite.exe 3.8.3)

create table /* This table has an educative purpose */ toto(x);
create table /* This table has an educative purpose */
   toty(x  );
create table
totz(x  );
select sql from sqlite_master;

... gives :
CREATE TABLE TOTO(X)
CREATE TABLE TOTY(X  )
CREATE TABLE
   TOTZ(X)

... instead of the original  full statements :
create table /* This table has an educative purpose */ toto(x)
create table /* This table has an educative purpose */
   toty(x  )
create table
totz(x  )


This sounds quite illogical, as :
-  Newlines and spaces are kept, (if not around a comment)
-  the SQLite internal parser would re-parse (and remove comments) from the
original statement without issue.


==> Would it be possible to keep comments, without loosing compatibility ?

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

Re: [sqlite] Comments in files intended for .read

[Simon Slavin]

On 30 Aug 2011, at 2:47pm, Richard Hipp wrote:

> On Tue, Aug 30, 2011 at 9:25 AM, Simon Slavin  wrote:
> 
>> Any problems with multi-line
>> quoted text strings containing comments ?  Anything else anyone wants to
>> warn me about ?  I don't actually need to use the '/*' format, but if anyone
>> wants to talk about that, that's cool too.
> 
> Strings that contain comment-like characters are not altered in any way -
> the comment-like characters are preserved.  The sqlite3_complete() routine
> takes care of this on behalf of the shell.

So ...

a) comment starters outside of statements introduce comments
b) comment starters inside of statements but outside of strings introduce 
comments
c) comment starters inside of strings are treated as part of the string

That checks with what I got when I experimented.  And I can work with that.  
Thanks.

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

Re: [sqlite] Comments in files intended for .read

[Richard Hipp]

On Tue, Aug 30, 2011 at 9:25 AM, Simon Slavin  wrote:

> I'm writing an app which generates text files intended for reading by the
> shell tool's '.read' command.  We're using SQL text files because I'm
> writing a design which needs to be completely open, understandable, and
> easily hackable by third parties.
>
> I want to include comments in my SQL files.  The following page
>
> 
>
> suggests I can use lines that begin with two consecutive "-" characters
> (ASCII 0x2d).  I have done some exploration to find out how the current
> version of the shell tool handles '--' inside quotes, inside
> statements, etc. but since it's not documented I can't be sure future
> versions will last the same way.
>
> Is anyone aware of any problems with this ?  Any problems with multi-line
> quoted text strings containing comments ?  Anything else anyone wants to
> warn me about ?  I don't actually need to use the '/*' format, but if anyone
> wants to talk about that, that's cool too.
>

Strings that contain comment-like characters are not altered in any way -
the comment-like characters are preserved.  The sqlite3_complete() routine
takes care of this on behalf of the shell.


>
> Simon.
> ___
> 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

[sqlite] Comments in files intended for .read

[Simon Slavin]

I'm writing an app which generates text files intended for reading by the shell 
tool's '.read' command.  We're using SQL text files because I'm writing a 
design which needs to be completely open, understandable, and easily hackable 
by third parties.

I want to include comments in my SQL files.  The following page



suggests I can use lines that begin with two consecutive "-" characters (ASCII 
0x2d).  I have done some exploration to find out how the current version of the 
shell tool handles '--' inside quotes, inside statements, etc. but 
since it's not documented I can't be sure future versions will last the same 
way.

Is anyone aware of any problems with this ?  Any problems with multi-line 
quoted text strings containing comments ?  Anything else anyone wants to warn 
me about ?  I don't actually need to use the '/*' format, but if anyone wants 
to talk about that, that's cool too.

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

Re: [sqlite] Comments

[Simon Slavin]

On 1 Aug 2011, at 2:10pm, Richard Hipp wrote:

> On Mon, Aug 1, 2011 at 8:53 AM, Marco Bambini  wrote:
> 
>> Why this valid statement:
>> 
>> CREATE TABLE USER(
>>   id  text,   -- the id of the user
>>   nametext-- the name of the user
>> );
>> 
>> gives me a syntax error with sqlite 3.7.6.3?
> 
> Works for me.

Works for me under 3.7.5.  My guess is that you're including some non-printable 
character.  What syntax error message are you getting ?

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

Re: [sqlite] Comments

[Richard Hipp]

On Mon, Aug 1, 2011 at 8:53 AM, Marco Bambini  wrote:

> Why this valid statement:
>
> CREATE TABLE USER(
>id  text,   -- the id of the user
>nametext-- the name of the user
> );
>
> gives me a syntax error with sqlite 3.7.6.3?
>

Works for me.


>
> Thanks.
> --
> Marco Bambini
> http://www.sqlabs.com
>
>
>
>
>
>
>
>
> ___
> 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

[sqlite] Comments

[Marco Bambini]

Why this valid statement:

CREATE TABLE USER(
id  text,   -- the id of the user
nametext-- the name of the user
);

gives me a syntax error with sqlite 3.7.6.3?

Thanks.
--
Marco Bambini
http://www.sqlabs.com








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

Re: [sqlite] comments on db design

[Steffen Scheer]

Gerry Snyder wrote:
> steffen scheer wrote:
>> Hey all
>>
>> I want to use sqlite as a storage engine for DNA sequence data. It is 
>> part of a workflow engine for DNA processing. I was wondering whether i 
>> chose the right db design.
>>
>> The db holds information about DNA sequences. Arranged in three tables.
>> For every dna sequence one entry in all 3 tables will be made (1:1 
>> Relation). Data will be inserted once, never deleted, but some 
>> attributes get updated.
>>   
> To me, KISS (keep it simple, stupid) rules until its performance has 
> been shown to be unacceptable.
> 
> Surely you can create a dummy db file with nonsense data of typical size 
> all in a single table and see whether it meets your needs.
> 
> Keeping 2 or 3 tables in synch is not a difficult task, but it is a 
> potential source for error.

You are right. I merged seq_desc_static and seq_desc_var.
This was my initial design. In the majority of cases the first design
is the best. KISS rules


Steffen




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

Re: [sqlite] comments on db design

[Gerry Snyder]

steffen scheer wrote:
> Hey all
>
> I want to use sqlite as a storage engine for DNA sequence data. It is 
> part of a workflow engine for DNA processing. I was wondering whether i 
> chose the right db design.
>
> The db holds information about DNA sequences. Arranged in three tables.
> For every dna sequence one entry in all 3 tables will be made (1:1 
> Relation). Data will be inserted once, never deleted, but some 
> attributes get updated.
>   
To me, KISS (keep it simple, stupid) rules until its performance has 
been shown to be unacceptable.

Surely you can create a dummy db file with nonsense data of typical size 
all in a single table and see whether it meets your needs.

Keeping 2 or 3 tables in synch is not a difficult task, but it is a 
potential source for error.


HTH,

Gerry


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

[sqlite] comments on db design

[steffen scheer]

Hey all

I want to use sqlite as a storage engine for DNA sequence data. It is 
part of a workflow engine for DNA processing. I was wondering whether i 
chose the right db design.

The db holds information about DNA sequences. Arranged in three tables.
For every dna sequence one entry in all 3 tables will be made (1:1 
Relation). Data will be inserted once, never deleted, but some 
attributes get updated.

First a static description table which holds information about a DNA
sequence. The unique key, the source etc. Once inserted the data is 
never modified.

CREATE TABLE seq_desc_static(
 seq_id  INTEGER PRIMARY KEY
 file TEXT UNIQUE,
sample TEXT,
source TEXT,
type INTEGER
);


Second a static data table which holds the base sequence for every row 
from seq_desc_static, approx. 30 to 800 bases, and for each base two 
numerical values, a quality value (two digit) and a integer. This data 
will never be modified as well, but will be inserted after the 
seq_desc_static table is populated. This table gets huge.
The table seq_data is just a data storage, query only be seq_id

CREATE TABLE seq_data(
seq_id INTEGER PRIMARY KEY,
 base TEXT,
qual TEXT,
call TEXT
)';

During the processing of a dna sequence we will generate some additional
infos for every row of seq_desc_static. These informations are kept in 
the third table. This table will be updated often during processing.

CREATE TABLE seq_desc_var(
 seq_id INTEGER PRIMARY KEY,
clear_range TEXT,
classification INTEGER,
history TEXT
)

Most of the queries select rows from seq_desc_static and then join with 
the seq_data table to retrieve the data. My impression was that it is 
faster to put the big data in an extra table and to join. Am I right ?

Is it a good solution to create an extra table for the updated data 
'seq_desc_var' or should i put it in seq_desc_static table ?
Selecting all data includes two joins ! That is expensive.


Thanks for any comments




























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

Re: [sqlite] Why do you use SQLite? Comments for an article needed

[Lucas (a.k.a T-Bird or bsdfan3)]

I personally like it for embedded (in other applications) jobs because 
of its small code footprint compared to a RDBMS.


Tim Anderson wrote:


Many thanks to those who have commented (more are welcome of course;
though I won't be able to use all of them).

I'll post a link to the piece when it appears.

Thanks again

Tim

-
To unsubscribe, send email to [EMAIL PROTECTED]
-



 



-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] Why do you use SQLite? Comments for an article needed

[Tim Anderson]

Many thanks to those who have commented (more are welcome of course;
though I won't be able to use all of them).

I'll post a link to the piece when it appears.

Thanks again

Tim

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Why do you use SQLite? Comments for an article needed

[John Elrick]

A.J.Millan wrote:

John Elrick wrote:

  

Tim Anderson wrote:

We are working on a project for the Census Bureau and needed an
embeddable database that was zero configuration for the user and fast.
We evaluated SQLite against numerous competitors...



IMHO, a bit exaggerated the "numerous competitors" part of the sentence.  In
fact there are not so many dbases that match the proposed conditions for
it's Bureau.

  


We evaluated a total of six, including two which would have required 
some configuration by the user.  I guess it depends upon your definition 
of "numerous", but I'd personally accept a half dozen as fitting that 
fuzzy description.



John

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Why do you use SQLite? Comments for an article needed

[Clay Dowling]

Tim Anderson wrote:
> I'm writing an article about SQLite and I'd love to get some comments
> from users about why you use it. Performance? Features? Reliability?
> Cost? Is the open source aspect important? Anything else? For that
> matter, anything you really don't like about SQLite?
>
> You can email me at tim(at)itwriting.com or comment here if you prefer -
> but to use your quote I'd need at least a full name, what you do and the
> company you work for

I'm using SQLite as an intermediate database in a shrinkwrap product.  As
part of a major version upgrade we're moving data from a Paradox database
with little to no data normalization into a SQL Server database normalized
to Boyce-Cod normal form.  SQLite is used to keep track of primary keys in
the new database to be used later in the process for maintaining data
relations.

SQLite was chosen for the following reasons:

1. Easy deployment.
2. Zero configuration.
3. Easy API to access from Delphi.
4. Licensing costs
5. Speed.  Speed was the primary deciding factor, because these lookups
must be fast.

Clay Dowling
-- 
Simple Content Management
http://www.ceamus.com


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Why do you use SQLite? Comments for an article needed

[Jan Kandziora]

Am Donnerstag, 7. Juni 2007 19:49 schrieb Tim Anderson:
> I'm writing an article about SQLite and I'd love to get some comments
>
> >from users about why you use it. Performance? Features? Reliability?
>
> Cost? Is the open source aspect important? Anything else? For that
> matter, anything you really don't like about SQLite?
>
I prefer SQLite as for applications where a substancial amount of information 
otherwise would be stored in made-up-from-scratch file formats. As soon as you 
need more structure than key-value pairs, an SQL database comes in handy.
It's pretty easy to extend an application with a SQLite db backend. You don't 
have to run a database server process just for storing some tables. 

What I especially like about SQLite is it's Tcl language binding. We do a lot 
of programming and scripting in Tcl and SQLite's Tcl interface handles the 
variable quoting automatically, so SQL injection bugs are very unlikely to 
happen.

The ability to extend SQLite's features -- e.g. adding custom collation 
sequences -- easily is another ++ for me.


> You can email me at tim(at)itwriting.com or comment here if you prefer -
> but to use your quote I'd need at least a full name, what you do and the
> company you work for
>
My company TuxTAP develops and manufactures Linux based cash registers and 
electronic dispensers for restaurants.

Kind regards

Jan
-- 
The first law of demos:
 - never try to actually use the system for anything

Re: [sqlite] Why do you use SQLite? Comments for an article needed

[A.J.Millan]

John Elrick wrote:

> Tim Anderson wrote:
>
> We are working on a project for the Census Bureau and needed an
> embeddable database that was zero configuration for the user and fast.
> We evaluated SQLite against numerous competitors...

IMHO, a bit exaggerated the "numerous competitors" part of the sentence.  In
fact there are not so many dbases that match the proposed conditions for
it's Bureau.

A.J.Millan
ZATOR Systems


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] Why do you use SQLite? Comments for an article needed

[Samuel R. Neff]

We chose SQLite for many reasons:
- zero configuration/installation
- availability of wonderful ADO.NET 2.0 wrapper
- easily extensible with custom functions
- performance (4x faster than MSSQL in our tests)
- available commercial support

The only thing we don't like is the lack non-standard loose data type
behavior and lack of many data types (particularly dates).

Best regards,

Samuel Neff
Sr Software Engineer
B-Line Medical
http://www.blinemedical.com


---
We're Hiring! Seeking a passionate developer to join our team building
products. Position is in the Washington D.C. metro area. If interested
contact [EMAIL PROTECTED]
 
-Original Message-
From: Tim Anderson [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 07, 2007 1:50 PM
To: sqlite-users@sqlite.org
Subject: [sqlite] Why do you use SQLite? Comments for an article needed

I'm writing an article about SQLite and I'd love to get some comments
from users about why you use it. Performance? Features? Reliability?
Cost? Is the open source aspect important? Anything else? For that
matter, anything you really don't like about SQLite?

You can email me at tim(at)itwriting.com or comment here if you prefer -
but to use your quote I'd need at least a full name, what you do and the
company you work for

Thanks in advance for your help.

Tim
http://www.itwriting.com/blog



-
To unsubscribe, send email to [EMAIL PROTECTED]

-


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Why do you use SQLite? Comments for an article needed

[Eugen Stoianovici]

John Elrick wrote:

Tim Anderson wrote:

I'm writing an article about SQLite and I'd love to get some comments
from users about why you use it. Performance? Features? Reliability?
Cost? Is the open source aspect important? Anything else? For that
matter, anything you really don't like about SQLite?

You can email me at tim(at)itwriting.com or comment here if you prefer -
but to use your quote I'd need at least a full name, what you do and the
company you work for

Thanks in advance for your help.
  
I'm mainly using it for development testing. It's really easy to migrate 
to other systems once you reach production stage.


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Why do you use SQLite? Comments for an article needed

[John Elrick]

Tim Anderson wrote:

I'm writing an article about SQLite and I'd love to get some comments
from users about why you use it. Performance? Features? Reliability?
Cost? Is the open source aspect important? Anything else? For that
matter, anything you really don't like about SQLite?

You can email me at tim(at)itwriting.com or comment here if you prefer -
but to use your quote I'd need at least a full name, what you do and the
company you work for

Thanks in advance for your help.
  



We are working on a project for the Census Bureau and needed an 
embeddable database that was zero configuration for the user and fast.  
We evaluated SQLite against numerous competitors and it came out on top 
for the following reasons:


1.  No licensing costs.  The application will be widely distributed at 
no charge to the user and therefore must be zero or minimal cost per 
license.

2.  Active support community.
3.  Mature library
4.  Source readily available
5.  Zero config.  One of our requirements is to ensure minimal burden to 
our users.
6.  Fast.  We have some requirements tied to performance, and SQLite met 
all of them handily.



John Elrick
Software Designer/Developer
Fenestra Technologies

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Why do you use SQLite? Comments for an article needed

[BardzoTajneKonto]

> I'm writing an article about SQLite and I'd love to get some comments
> from users about why you use it. Performance? Features? Reliability?
> Cost? 

- no restrictions, like only 1 LONG VARCHAR in the table, numer of columns, 
maximum network packet size and similar (actually there are some 
restrictions regarding sizes, but with resonable max values)
- fast
- open source
- free

>Is the open source aspect important? 

Very. I don't work with orygnal SQLite, but with customized version.

> For that
> matter, anything you really don't like about SQLite?

- no full support for ALTER TABLE and JOIN
- no strict typing and missing date type
- no high concurrency support


Wiktor Adamski



--
Wicie, rozumicie
Zobacz >>> http://link.interia.pl/f1a74


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Why do you use SQLite? Comments for an article needed

[Alberto Simões]

Hi, Tim.

We are using SQLite for two main reasons:
- no daemon needed: to use RDBMS on a cluster machine is quite
annoying. Most clusters administrators does not want more daemons
running.
- SQLite can be very fast when you tweak some of its basic
configuration pragmas, being more than 200% faster than MySQL or
Postgres on batch insert operations.

Hope this can at least give you some ideas for your article.

Good luck
Alberto

On 6/7/07, Tim Anderson <[EMAIL PROTECTED]> wrote:

I'm writing an article about SQLite and I'd love to get some comments
from users about why you use it. Performance? Features? Reliability?
Cost? Is the open source aspect important? Anything else? For that
matter, anything you really don't like about SQLite?

You can email me at tim(at)itwriting.com or comment here if you prefer -
but to use your quote I'd need at least a full name, what you do and the
company you work for

Thanks in advance for your help.

Tim
http://www.itwriting.com/blog


-
To unsubscribe, send email to [EMAIL PROTECTED]
-





--
Alberto Simões

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Why do you use SQLite? Comments for an article needed

[Cesar D. Rodas]

I am using SQLite because it is easy to use (zero config). To add to your
project.  And it was  well designed by Mr. Hipp, with a really to use API. A
wild SQL support.
Because there is not Client-Server, and thousands times better than access
and foxpro
Many people uses, so there is a lot of help.
A lot wrappers for C++, PHP, Python, Ruby on rails, and others.
Because it is done in C, it will have a great performance


A proof of the power of SQLite is that is used in Google Gear Project.

On 07/06/07, Tim Anderson <[EMAIL PROTECTED]> wrote:


I'm writing an article about SQLite and I'd love to get some comments
from users about why you use it. Performance? Features? Reliability?
Cost? Is the open source aspect important? Anything else? For that
matter, anything you really don't like about SQLite?

You can email me at tim(at)itwriting.com or comment here if you prefer -
but to use your quote I'd need at least a full name, what you do and the
company you work for

Thanks in advance for your help.

Tim
http://www.itwriting.com/blog



-
To unsubscribe, send email to [EMAIL PROTECTED]

-





--
Cesar Rodas
http://www.cesarodas.com/
Mobile Phone: 595 961 974165
Phone: 595 21 645590
[EMAIL PROTECTED]
[EMAIL PROTECTED]

[sqlite] Why do you use SQLite? Comments for an article needed

[Tim Anderson]

I'm writing an article about SQLite and I'd love to get some comments
from users about why you use it. Performance? Features? Reliability?
Cost? Is the open source aspect important? Anything else? For that
matter, anything you really don't like about SQLite?

You can email me at tim(at)itwriting.com or comment here if you prefer -
but to use your quote I'd need at least a full name, what you do and the
company you work for

Thanks in advance for your help.

Tim
http://www.itwriting.com/blog


-
To unsubscribe, send email to [EMAIL PROTECTED]
-