At 6:02 PM -0400 9/18/04, D. Richard Hipp wrote:
SQLite version 3.0.7 is now available on the website.
With this release, SQLite version 3.0 leaves beta and
becomes "stable".
And I thank-a-you :)
-- Darren Duncan
SQLite version 3.0.7 is now available on the website.
With this release, SQLite version 3.0 leaves beta and
becomes "stable".
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
On Sat, Sep 18, 2004 at 04:58:53PM -0400, D. Richard Hipp wrote:
> [EMAIL PROTECTED] wrote:
> >I am working with triggers on a field defined in a table
> >as INTEGER PRIMARY KEY. Agreed, triggers are not fully
> >implemented on int primary key; but, I need the autoincrement
> >feature.
> >
> >I
[EMAIL PROTECTED] wrote:
I am working with triggers on a field defined in a table
as INTEGER PRIMARY KEY. Agreed, triggers are not fully
implemented on int primary key; but, I need the autoincrement
feature.
I always get -1. Can I depend on that -1 until this feature
is implemented?
If you
At 3:41 PM -0400 9/18/04, D. Richard Hipp wrote:
Check the website ;-)
Well now! Aren't *we* happy as a clam!
A new chapter in SQLite history begins today ...
-- Darren Duncan
I am working with triggers on a field defined in a table
as INTEGER PRIMARY KEY. Agreed, triggers are not fully
implemented on int primary key; but, I need the autoincrement
feature.
I always get -1. Can I depend on that -1 until this feature
is implemented?
Here is an example. There are two
Darren Duncan wrote:
At 10:04 AM -0400 9/18/04, D. Richard Hipp wrote:
That problem was fixed on Sep 6 by check-in [1941].
See http://www.sqlite.org/cvstrac/chngview?cn=1941
While there are issues going on that prevent a move to 'production
status' before the end of the month, would it be too
At 10:04 AM -0400 9/18/04, D. Richard Hipp wrote:
That problem was fixed on Sep 6 by check-in [1941].
See http://www.sqlite.org/cvstrac/chngview?cn=1941
While there are issues going on that prevent a move to 'production
status' before the end of the month, would it be too much trouble to
release
say you have the following logic:
begin transaction in parent
if pid = fork
commit transaction
close database
else
close database
...
end
should this be o.k.? i notice the unlink of the db-journal will happen twice
- which should be o.k. but will flush/sync
Marco Bambini wrote:
both sqlite.h and sqlite3.h begins with:
#ifndef _SQLITE_H_
#define _SQLITE_H_
...
#endif
Any solution?
That problem was fixed on Sep 6 by check-in [1941].
See http://www.sqlite.org/cvstrac/chngview?cn=1941
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
Hi,
I have to develop an application that can use both sqlite2 dbs and
sqlite3 dbs.
I have compiled fine both the libraries and my trial code looks like:
#include
#include "sqlite.h"
#include "sqlite3.h"
int main(int argc, char *argv[])
{
int err;
sqlite
11 matches
Mail list logo