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
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
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
>
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 */
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
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
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
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
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
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
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
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
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
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 */
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 '/*'
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
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.
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
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.
>
>
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
___
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
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
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
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
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
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
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
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
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
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
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
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
> 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
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%
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
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
36 matches
Mail list logo