On 11 Sep 2009, at 6:56pm, Dan Kennedy wrote:
> On Sep 12, 2009, at 12:01 AM, Simon Slavin wrote:
>
>> May I ask what happens if SQLITE_MAX_TRIGGER_DEPTH is reached ? Is
>> an
>> error generated ? Is a transaction marked as failed, etc. ?
>
> The statement execution fails with SQLITE_ERROR.
On Sep 12, 2009, at 12:01 AM, Simon Slavin wrote:
>
> On 11 Sep 2009, at 5:45pm, D. Richard Hipp wrote:
>
>> The second major enhancement is that SQLite now support recursive
>> triggers. The older non-recursive behavior of triggers is still the
>> default behavior. Recursive triggers are
On Fri, Sep 11, 2009 at 12:45:44PM -0400, D.Richard Hipp scratched on the wall:
> The second major enhancement is that SQLite now support recursive
> triggers.
I assume this provides a significantly better support for foreign key
constraints through the genfkey command.
Has anyone had
On 11 Sep 2009, at 5:45pm, D. Richard Hipp wrote:
> The second major enhancement is that SQLite now support recursive
> triggers. The older non-recursive behavior of triggers is still the
> default behavior. Recursive triggers are activated using the
> recursive_triggers pragma. In addition to
SQLite version 3.6.18 is now available for download from the SQLite
website.
http://www.sqlite.org/
The SQLite source code is tracked and managed using the Fossil
distributed configuration management system. See http://www.fossil-scm.org/
for further information on Fossil. SQLite was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
D. Richard Hipp wrote:
> There are multiple reasons for changing from CVS to Fossil.
The reasons listed are true for pretty much any of the current popular
distributed source control systems. They have various minor under the hood
differences (eg if
> So what are we missing. Can you suggest better ways of organizing the
> documentation above?
A bit of suggestion: it would be great if
http://www.sqlite.org/doc_keyword_crossref.html was accessible from
http://www.sqlite.org/docs.html as a link say after "FAQ" with a text
like "All
ers-boun...@sqlite.org] On Behalf Of D. Richard Hipp
> Sent: Wednesday, September 09, 2009 2:29 PM
> To: General Discussion of SQLite Database
> Subject: Re: [sqlite] SQLite version 3.6.18 scheduled for Monday
>
>
> On Sep 9, 2009, at 2:04 PM, Shaun Seckman (Firaxis) wrote:
>
&
On Sep 9, 2009, at 1:46 PM, John Loveys wrote:
>
> I do find the documentation rather awkward. I have seen (and used)
> links to
> stuff I cannot find from the start page. Maybe doxygen? I write a
> lot of C
> and find it invaluable.
>
Suggestions on how to improve the documentation are
of SQLite Database
Subject: Re: [sqlite] SQLite version 3.6.18 scheduled for Monday
On Sep 9, 2009, at 2:04 PM, Shaun Seckman (Firaxis) wrote:
> It's always a pleasure to have a new version of one of my favorite
> tools. I noticed in the draft that you migrated the project to
> Fossi
On Sep 9, 2009, at 2:04 PM, Shaun Seckman (Firaxis) wrote:
> It's always a pleasure to have a new version of one of my favorite
> tools. I noticed in the draft that you migrated the project to
> Fossil.
> I am curious, how was your experience with the migration? Did it go
> smoothly or were
for migrating in the first place?
-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of D. Richard Hipp
Sent: Wednesday, September 09, 2009 11:55 AM
To: General Discussion of SQLite Database
Subject: [sqlite] SQLite version 3.6.18
a glass...
Cheers
/J
-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of D. Richard Hipp
Sent: Wednesday, September 09, 2009 12:55 PM
To: General Discussion of SQLite Database
Subject: [sqlite] SQLite version 3.6.18 scheduled for Monday
We are on schedule to release SQLite version 3.6.18 on Monday,
2009-09-14. For a preview, see
http://www.sqlite.org/draft/index.html
D. Richard Hipp
d...@hwaci.com
___
sqlite-users mailing list
sqlite-users@sqlite.org
14 matches
Mail list logo