Re: [sqlite] Path Length Limit on Windows

Hi, Richard, Von Richard Hipp > On Mon, Aug 26, 2013 at 10:39 AM, Markus Schaber wrote: > > Having a closer look, this will only solve problems with pathes whose > > UTF8-encoding is longer than MAX_PATH bytes, but not with pathes which > > exceed the 260 character limit. >

[sqlite] auto_vacuum default setting

When I look through details about PRAGMA auto_vacuum,I think it is always beneficial to have auto_vaccum set to Full so that whenever delete happens we have shrink of size. http://www.sqlite.org/pragma.html#pragma_auto_vacuum I wanted to know is their any benefit to have this to none in default

Re: [sqlite] auto_vacuum default setting

techi eth wrote: > When I look through details about PRAGMA auto_vacuum,I think it is always > beneficial to have auto_vaccum set to Full so that whenever delete happens we > have shrink of size. > > I wanted to know is their any benefit to have this to none in default > instead of full. 1.

Re: [sqlite] auto_vacuum default setting

How on #3? I thought it did a complete dump to a new file? On Thu, Aug 29, 2013 at 3:03 AM, Clemens Ladisch wrote: > techi eth wrote: > > When I look through details about PRAGMA auto_vacuum,I think it is always > > beneficial to have auto_vaccum set to Full so that

[sqlite] segmentation fault with 3.8.0

Hi. I've just got a segmentation fault report with SQLite 3.8.0 from one of the perl binding users. The following set of SQL statements should reporduce the issue. Regards, Kenichi Ishigaki CREATE TABLE "twokeys" ( "artist" integer NOT NULL, "cd" integer NOT NULL, PRIMARY KEY ("artist", "cd")

[sqlite] Database File Size

Database files size: 1) Is their any way I can calculate approx file size based on data. Ex : Let us say i am creating table with (row ID int ,Test Text). Each text string size is 10 byte. If I will create 100 row of this in database then what would be Max size of created database file.

Re: [sqlite] auto_vacuum default setting

Stephen Chrzanowski wrote: > On Thu, Aug 29, 2013 at 3:03 AM, Clemens Ladisch wrote: >> 3. auto_vacuum will increase fragmentation > > I thought it did a complete dump to a new file? says: | Auto-vacuum does not

[sqlite] Sqlite3 on JFFS2 File System

Hi, Anybody have used Sqlite3 on JFFS2 file system with Journal_mode = WAL. I have found issue of I/O error. Thanks ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Database locking Error

On 29 Aug 2013, at 6:48am, techi eth wrote: > I am checking for all the function.As of now i am not using sqlite3 time > out but testing application will take decision accordingly to recall the > operation based on type of error. If you have two simultaneous processes

Re: [sqlite] Database File Size

On 29 Aug 2013, at 9:11am, techi eth wrote: > 1) Is their any way I can calculate approx file size based on data. > > Ex : Let us say i am creating table with (row ID int ,Test Text). > > Each text string size is 10 byte. If I will create 100 row of this in >

Re: [sqlite] auto_vacuum default setting

On 29 Aug 2013, at 9:16am, techi eth wrote: > Here I am looking what is best strategy sqlite3 provide for database > purging.What combination of auto vacuum & vacuum to be used? > > I have started using sqlite from few weeks so answer from experience will > help me. If you

Re: [sqlite] auto_vacuum default setting

Ahhh.. Thats the difference. Auto_Vacuum versus Vacuum pragmas. doh. Shoulda thought of that. I blame 2am. On Thu, Aug 29, 2013 at 5:43 AM, Clemens Ladisch wrote: > Stephen Chrzanowski wrote: > > On Thu, Aug 29, 2013 at 3:03 AM, Clemens Ladisch >

Re: [sqlite] segmentation fault with 3.8.0

My guess is single quotes instead of double quotes. Where exactly is the seg fault? Untested but other than the quotes, everything looks fine. On Thu, Aug 29, 2013 at 4:07 AM, kenichi ishigaki wrote: > Hi. I've just got a segmentation fault report with SQLite 3.8.0 from

Re: [sqlite] segmentation fault with 3.8.0

On Thu, Aug 29, 2013 at 11:32 AM, Stephen Chrzanowski wrote: > My guess is single quotes instead of double quotes. Where exactly is the > seg fault? Untested but other than the quotes, everything looks fine. > The problem is described here:

Re: [sqlite] segmentation fault with 3.8.0

On Thu, Aug 29, 2013 at 11:38 AM, Richard Hipp wrote: > > > A patch release 3.8.0.1 that includes this fix and fixes for two other > equally obscure corner cases is currently in test and is expected to go out > later today. > > Complete set of diffs for the proposed patch

Re: [sqlite] auto_vacuum default setting

auto_vacuum at full is slower: When you delete some data, SQLite would shrink the file size to the minimum. If, in the next transaction, you add new data, SQLite would again have to extend the file size by at least a page. This takes time. Without auto-vacuum=FULL, the Insert statement would

Re: [sqlite] segmentation fault with 3.8.0

Silly question.. I looked at the fix. Why ignore indexes with greater than 4 fields? Isn't that a bit risky? Wouldn't it be better to ignore the fields after the 4th one for planning? -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org]

Re: [sqlite] segmentation fault with 3.8.0

On Thu, Aug 29, 2013 at 11:47 AM, Marc L. Allen wrote: > Silly question.. I looked at the fix. Why ignore indexes with greater > than 4 fields? Isn't that a bit risky? Wouldn't it be better to ignore > the fields after the 4th one for planning? > The

Re: [sqlite] segmentation fault with 3.8.0

On 08/29/2013 10:47 PM, Marc L. Allen wrote: Silly question.. I looked at the fix. Why ignore indexes with greater than 4 fields? Isn't that a bit risky? Wouldn't it be better to ignore the fields after the 4th one for planning? SQLite 3.8.0 really contains two query planners. The first

Re: [sqlite] segmentation fault with 3.8.0

Thanks... that certainly clarifies it. Also, thanks to Dan who responded similarly. -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Richard Hipp Sent: Thursday, August 29, 2013 11:58 AM To: General Discussion of SQLite

[sqlite] Changed behavior from 3.7.17 to 3.8.0.

I don't know if this is serious, but a SAVEPOINT command fails with an open statement handle used to execute PRAGMA journal_mode = off at SQLite 3.8.0, but appears to succeed at SQLite 3.7.17.  This does not appear to be documented.  Note that a BEGIN TRANSACTION will appear to succeed where

Re: [sqlite] Path Length Limit on Windows

>Date: Wed, 28 Aug 2013 14:21:24 -0400 >From: Richard Hipp > >The latest check-in on trunk adds a new windows VFS module called >"win32-longpath" which accepts the full-length 32KB pathnames. Add the >string "win32-longpath" as the 4th argument to sqlite3_open_v2() (on >windows

Re: [sqlite] segmentation fault with 3.8.0

Thank you for the fix! Kenichi Ishigaki 2013/8/30 Marc L. Allen : > Thanks... that certainly clarifies it. Also, thanks to Dan who responded > similarly. > > -Original Message- > From: sqlite-users-boun...@sqlite.org >

[sqlite] [sqlite-users] -DSQLITE_ENABLE_LOCKING_STYLE=1 doesn't work on Linux/Cygwin

The effect of SQLITE_ENABLE_LOCKING_STYLE=1 on platforms other than VXWORKS or OSX is documented to enable the flock locking style, which is available just fine on Linux and Cygwin. So this should work fine: $ gcc -c -DSQLITE_ENABLE_LOCKING_STYLE=1 -DSQLITE_OS_UNIX=1 sqlite3.c sqlite3.c: In

Re: [sqlite] BETWEEN and explicit collation assignment

On Tue, 27 Aug 2013 21:00:50 -0500 Nico Williams wrote: > Of course, lacking a syntax for associating collations with string > literals there will be times when some, or even all of the operands to > an operation that needs collation information, is missing. In such >

Re: [sqlite] Database locking Error

Thanks for suggestion. I will take it forward. locking will happen with two simultaneous processes accessing for read also? Thanks On 8/29/13, Simon Slavin wrote: > > On 29 Aug 2013, at 6:48am, techi eth wrote: > >> I am checking for all the

Re: [sqlite] Database File Size

I am using Jffs2 file system. As of now I using all default from sqlite3.I am not sure with this information it is possible to get some approx that with 'X KB data, database file size will be 'Y' KB or MB. > Regarding default file size. I understand with the use of max_page_count & size of each

Re: [sqlite] Database File Size

I am thinking to use auto_vacuum INCREMENTAL & PRAGMA incremental_vacuum(N) to make sure whenever required, pages can be free. I assume this will be better option with compare to FULL. I assume i can do anytime this operation in squence after opening successfull connection to Database.I am