2014-01-28 James Turner:
Thanks for the clarification guys. I'm thinking it's probably safe then
to use 1.28 with our 3.8.0.2 version of SQLite.
I'll get our in-tree version of SQLite upgraded to the latest after the
unlock.
Thanks for your feedback. It is highly appreciated!
Regards,
I think URL like:.../tree?ci=trunk will fail without 3.8.2.
Your best bet is to compile without --disable-internal-sqlite and just let
Fossil use the built-in version of SQLite. That will definitely be the
safest and best tested approach. If you use --disable-interal-sqlite, you
never know
On Mon, Jan 27, 2014 at 5:54 PM, Jan Nijtmans jan.nijtm...@gmail.comwrote:
2014-01-27 Richard Hipp d...@sqlite.org:
I think URL like:.../tree?ci=trunk will fail without 3.8.2.
This is the url which uses WITHOUT ROWID in trunk, but
thanks to the SQLite version check it doesn't depend
2014-01-28 Richard Hipp d...@sqlite.org:
FWIW, Fossil 1.29 will very definitely require SQLite 3.8.3 or later in as
much as it uses common table expressions to help generate the timeline now.
Yes, and I'm looking forward to that! By the time that Fossil 1.29
will be released, SQLite 3.8.3 will
On Mon, Jan 27, 2014 at 06:01:42PM -0500, Richard Hipp wrote:
On Mon, Jan 27, 2014 at 5:54 PM, Jan Nijtmans jan.nijtm...@gmail.comwrote:
2014-01-27 Richard Hipp d...@sqlite.org:
I think URL like:.../tree?ci=trunk will fail without 3.8.2.
This is the url which uses WITHOUT ROWID
5 matches
Mail list logo
