Re: [sqlite] Output/CSV

On 1/12/18, John Gutierrez wrote: > Sqlite Shell: > > On Linux, using .output and .mode csv, sqlite produces a [dos] 1L, 161C > file. Is this a bug or is it a compile issue for my distribution to > address? I don't know what a "[dos] 1L, 161C" file is? Can you explain?

[sqlite] Output/CSV

Sqlite Shell: On Linux, using .output and .mode csv, sqlite produces a [dos] 1L, 161C file. Is this a bug or is it a compile issue for my distribution to address? ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

Re: [sqlite] EXTERNAL: SQLite 3.22.0 coming soon

Am Wed, 10 Jan 2018 02:25:35 + schrieb Edwards, Mark C.: > Release mode/x86 Visual Studio 2015 Prono problems with the new snapshot Same here with my ancient Visual Studio 2005. :-) Cheers Wolfgang ___ sqlite-users mailing list

[sqlite] database type graph

How can I design in a database a database type graph? thank This message was sent using IMP, the Internet Messaging Program. -- Este mensaje le ha llegado mediante el servicio de correo electronico que ofrece Infomed para

Re: [sqlite] pcache1FetchStage2 CRASH

On 1/12/18, zheng xiaojin wrote: > I am using the 3.15.2, and currently a problem comes to me that, > pcache1FetchStage2 CRASH when access the pgroup->lru.pLRUPrev->isAnchor, the > crash info is sigsegv access 0x16 on IOS. > And a little frequently about0.1percent.

Re: [sqlite] os_unix.c:36136: (2)

On 1/11/18, wei1.z wrote: > What is the meaning of this line? > > 01-11 14:40:59.733 10011 2864 2877 E SQLiteLog: (14) os_unix.c:36136: (2) > open() - > > db file cannot be found, or permission issue ? It means that SQLite could not open a file either because that file

[sqlite] pcache1FetchStage2 CRASH

I am using the 3.15.2, and currently a problem comes to me that, pcache1FetchStage2 CRASH when access the pgroup->lru.pLRUPrev->isAnchor, the crash info is sigsegv access 0x16 on IOS. And a little frequently about0.1percent. 获取 Outlook for Android

[sqlite] os_unix.c:36136: (2)

What is the meaning of this line? 01-11 14:40:59.733 10011 2864 2877 E SQLiteLog: (14) os_unix.c:36136: (2) open() - db file cannot be found, or permission issue ? Thanks a lot! -- Sent from: http://sqlite.1065341.n5.nabble.com/ ___ sqlite-users

Re: [sqlite] SQLite 3.22.0 coming soon

On 1/12/18, petern wrote: > Is adding arg_count and > is_aggregate columns to PRAGMA function_list() on the roadmap? How would that work with functions like coalesce() and max() that take an arbitrary number of arguments, or like max() that is an aggregate with one

Re: [sqlite] SQLite 3.22.0 coming soon

This is premature of course. The columns of the current PRAGMA function_list() report do not form a practical key for functions. Additional columns arg_count and is_aggregate would be needed join PRAGMA function_list() with a function description table. Suggestion: As an example of both testing

Re: [sqlite] Is foreign key support disabled within triggers with raise functions?

I think the thing here is... "...But the FAIL resolution does not back out prior changes of the SQL statement that failed ..." Emphasis on the last part. So you would think that in autocommit mode you would wind up in the middle of your "implicitly created" transaction, which you could then

Re: [sqlite] SQLite 3.22.0 coming soon

Ryan. The core and sqlite3_create_function...() needn't be burdened at all except to store some very basic description strings as a compile time option. PRAGMA function_list() cold gather descriptions on the fly by: 1. Spinning through the list of registered %_function_description(F,N)

Re: [sqlite] Efficient ways to maintaining order rank / row_number() in a rather large set ?

On 12 Jan 2018, at 10:31am, Eric Grange wrote: > >> This should not be true. You should not be using OFFSET. Your queries >> should be something like > > That was with only the "value" field being indexed (so without a rank > field), is there a better way than OFFSET in

Re: [sqlite] Is foreign key support disabled within triggers with raise functions?

On 1/12/18, Shane Dev wrote: > Does that mean FK constraints are only checked > if processing reaches the end of the trigger? FKs are checked at the end of the entire statement. If multiple triggers fire, then they all run to completion before any FKs are checked. -- D.

Re: [sqlite] Is foreign key support disabled within triggers with raise functions?

Thanks for the explanation. Does that mean FK constraints are only checked if processing reaches the end of the trigger? On 12 January 2018 at 13:29, Richard Hipp wrote: > Test 1 makes the changes, the checks the FK constraints, sees that the > FK constraints are violated and

Re: [sqlite] Is foreign key support disabled within triggers with raise functions?

Test 1 makes the changes, the checks the FK constraints, sees that the FK constraints are violated and hence runs ABORT, which backs out the change. Test 2 makes the change, then runs FAIL, which stops all further processing. The FK constraints are never checked, and the changes are not backed

Re: [sqlite] Is foreign key support disabled within triggers with raise functions?

Hello, Perhaps it would be clearer if I ask the question in a different way. Why does the following statement - insert into vtrig select 5; fail to insert a record in Test 1 below (as expected) but succeeds in Test 2 (despite the foreign key constraint)? sqlite> CREATE TABLE reftab(id integer

Re: [sqlite] Efficient ways to maintaining order rank / row_number() in a rather large set ?

> But if you have million rows this could involve a lot of number-shuffling and I can see that it might not work out in the real world. Yes, also while value field can change several times per seconds (thousandths in some cases), it is acceptable to have the ranking be updated at a lower

Re: [sqlite] sqlite3_column_decltype and max and min

Thanks Warren. Sorry about that, I had an old version in /opt/local/bin. John Gillespie On 11 January 2018 at 15:24, Warren Young wrote: > On Jan 11, 2018, at 5:47 AM, John G wrote: > > > > Is this because I am stuck with version 3.8.8.3 which is