On 2/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
DragonK <[EMAIL PROTECTED]> wrote:
>
> So, as I understand it, this is supported from version 3.3.8 upwards,
right?
>
Correct.
Thanks for straigthening out the issue! :)
--
D. Richard Hipp <[EMAIL PROTECTED]>
-
May I ask what the dev plan is for SQLIte?
For example, out of the missing SQL-92 features, what is likely to be
implemented first to complete the standard?
I would like to see referential integrity natively enforced No.1 and then
support for stored procedures with cached query plans.
Thanks,
Artem Yankovskiy
wrote:
I like delete some of table.
DROP TABLE tableName;
http://sqlite.org/lang_droptable.html
Igor Tandetnik
-
To unsubscribe, send email to [EMAIL PROTECTED]
Yesterday I trapped myself in sqlite3 and could not exit the application.
I was running the SQLite shell in a virtual console and inadvertently
entered ',e' instead of '.e' to exit.
Cue the theme from 'Jaws.' I was trapped and could not escape. Not, that
is, until I went to another vc and kil
This might be a dumb question, but is taking a backup of a live database
simply a matter of copying the file to a backup device/drive?
And restoring it a matter of copying it back?
I am using Windows with NTFS drives.
--
View this message in context:
http://www.nabble.com/Backing-up-a-SQlite
hmmm, I don't know what a "virtual console" is but on my computer...
Lucknow:~ punkish$ sqlite3 foo.db
SQLite version 3.3.8
Enter ".help" for instructions
sqlite> ,e
...> ;
SQL error: near ",": syntax error
sqlite> .q
Lucknow:~ punkish$
On 2/9/07, Rich Shepard <[EMAIL PROTECTED]> wrote:
Ye
On Fri, 9 Feb 2007, P Kishor wrote:
hmmm, I don't know what a "virtual console" is but on my computer...
That's a console in X that looks like a regular terminal console. I use
rxvt, others use xterm, eterm, aterm, etc.
Lucknow:~ punkish$ sqlite3 foo.db
SQLite version 3.3.8
Enter ".help" f
On Fri, 9 Feb 2007, Mikey C wrote:
This might be a dumb question, but is taking a backup of a live database
simply a matter of copying the file to a backup device/drive?
Yes. It's a regular file to your OS. As a matter of fact, you can copy the
file to another name and open that other name t
On 2/9/07, Rich Shepard <[EMAIL PROTECTED]> wrote:
On Fri, 9 Feb 2007, Mikey C wrote:
> This might be a dumb question, but is taking a backup of a live database
> simply a matter of copying the file to a backup device/drive?
Yes. It's a regular file to your OS. As a matter of fact, you can c
Rich Shepard wrote:
Yesterday I trapped myself in sqlite3 and could not exit the application.
I was running the SQLite shell in a virtual console and inadvertently
entered ',e' instead of '.e' to exit.
Cue the theme from 'Jaws.' I was trapped and could not escape. Not, that
is, until I went
Rich Shepard uttered:
On Fri, 9 Feb 2007, Mikey C wrote:
This might be a dumb question, but is taking a backup of a live database
simply a matter of copying the file to a backup device/drive?
Yes. It's a regular file to your OS. As a matter of fact, you can copy the
file to another name and
Rich Shepard <[EMAIL PROTECTED]> writes:
> On Fri, 9 Feb 2007, Mikey C wrote:
>
>> This might be a dumb question, but is taking a backup of a live database
>> simply a matter of copying the file to a backup device/drive?
>
> Yes. It's a regular file to your OS. As a matter of fact, you can copy
Thanks Artem. Your description of events agrees with the documentation and
what I would expect to happen, but not with what I'm observing in running
code.
I see that the sqlite_step() for the "COMMIT TRANSACTION" returns
SQLITE_DONE, but then the changes in the transaction have been rolled back.
On Fri, 9 Feb 2007, Christian Smith wrote:
No, no, no! Copying the file is not atomic, and a live database may be
updated part way through the copy.
Mea culpa! My response was based on my own use of sqlite, which is
embedded in models. Therefore, when I do any copying of the database file
it
It looks like the journal file itself is running out of disk space. It has
only 512 bytes, even though I'm creating lots of tables in the transaction,
and the DB file itself is stuck at 0 bytes. Then, COMMIT TRANSACTION
returns SQLITE_DONE, the journal file disappears, and I'm left with a db of
[EMAIL PROTECTED] wrote:
You should either have your backup application open the database and do a
BEGIN EXCLUSIVE; statement to ensure that no other processes can write to it
while you're backing it up, or if you don't want to do that, you can use the
command line shell and do:
sqlite3 .dump
Debugging the code:
winWrite returns SQLITE_FULL, which propagates back up the stack to
vdbeaux.c, line 1270, in function sqlite3VdbeHalt(Vdbe *p):
}else if( rc!=SQLITE_OK ){
p->rc = rc;
sqlite3RollbackAll(db);
Which is good, it's putting the SQLITE_FULL return code into
[EMAIL PROTECTED] wrote:
You should either have your backup application open the database and do a
BEGIN EXCLUSIVE; statement to ensure that no other processes can write to it
while you're backing it up
Derrell,
Just to clarify, you don't need to use an exclusive transaction. That
will a
Jeffrey Rennie wrote:
Debugging the code:
winWrite returns SQLITE_FULL, which propagates back up the stack to
vdbeaux.c, line 1270, in function sqlite3VdbeHalt(Vdbe *p):
}else if( rc!=SQLITE_OK ){
p->rc = rc;
sqlite3RollbackAll(db);
Which is good, it's putting the SQLIT
Jeffrey Rennie wrote:
Debugging the code:
winWrite returns SQLITE_FULL, which propagates back up the stack to
vdbeaux.c, line 1270, in function sqlite3VdbeHalt(Vdbe *p):
}else if( rc!=SQLITE_OK ){
p->rc = rc;
sqlite3RollbackAll(db);
Which is good, it's putting the SQLIT
Thanks for your help, guys,
It now makes sense.
Rick van der Lans
-Oorspronkelijk bericht-
Van: Doug Currie [mailto:[EMAIL PROTECTED]
Verzonden: Wednesday, January 31, 2007 4:16 PM
Aan: sqlite-users@sqlite.org
Onderwerp: Re: [sqlite] Does julianday work according to the manual?
On Wedne
The manual mentions the support for the MATCH and the REGEXP operators. But
if I use it, it doesn't work. Do I have to do something special to install
those operators?
Regards,
Rick van der Lans
-
To unsubscribe, send
I think the code in the next higher stackframe may be the culprit.
I inserted a new line of code at vbde.c:2374 so it now reads:
if( pOp->p2 ){
assert( i==1 );
sqlite3RollbackAll(db);
db->autoCommit = 1;
}else{
db->autoCommit = i;
if( sqlite3VdbeHalt(p)==SQLITE_BUS
On Fri, 9 Feb 2007 21:11:31 +0100, Rick wrote:
>The manual mentions the support for the MATCH and the REGEXP operators. But
>if I use it, it doesn't work. Do I have to do something special to install
>those operators?
http://www.sqlite.org/lang_expr.html tells:
"The REGEXP operator is a special
Jeffrey Rennie wrote:
I think the code in the next higher stackframe may be the culprit.
I inserted a new line of code at vbde.c:2374 so it now reads:
if( pOp->p2 ){
assert( i==1 );
sqlite3RollbackAll(db);
db->autoCommit = 1;
}else{
db->autoCommit = i;
if( sqlite3
On 2/9/07, Dennis Cote <[EMAIL PROTECTED]> wrote:
Jeffrey Rennie wrote:
> I think the code in the next higher stackframe may be the culprit.
>
> I inserted a new line of code at vbde.c:2374 so it now reads:
>
>if( pOp->p2 ){
> assert( i==1 );
> sqlite3RollbackAll(db);
> db->au
On 2/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
"Stan Bielski" <[EMAIL PROTECTED]> wrote:
>
> Anyone care to take a guess what's going on here?
The problem is that you are thrashing. The working set
on the database file is exceeding the amount of memory
that your OS has set aside for d
I have no problems compiling under VS2005 using 3.3.12 when I don't
define SQLITE_OMIT_TRIGGER.
However, I do get an error compiling when I define SQLITE_OMIT_TRIGGER=1
The linker complains about sqlite3_enable_shared_cache not being
exported.
Is this just VS2005 wierdness, or is there a missing
So, if I understand correctly, SQLite does not support these two operators
"out of the box".
Is there an easy way to get user-defined functions for regexp and match? Or
has no one developed those yet?
Regards,
Rick van der Lans
-Oorspronkelijk bericht-
Van: Kees Nuyt [mailto:[EMAIL PROTEC
> I understand that I'm experiencing thrashing, but I'm curious as to why I'm
> experiencing it. My understanding is that the row_id PRIMARY KEY column has
> an index on it by default. Inserting into this index doesn't cause
> thrashing, but inserting into the secondary index does. I hoped that
> e
30 matches
Mail list logo
