Re: [sqlite] [EXTERNAL] one to one relationships

What is the question? -Ursprüngliche Nachricht- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Paul Alagna Gesendet: Dienstag, 17. Oktober 2017 08:35 An: sqlite-users@mailinglists.sqlite.org Betreff: [EXTERNAL] [sqlite] one to one relationships 2 t

Re: [sqlite] [EXTERNAL] current_timestamp locale

There is no "DATE" type in SQLite. The current_timestamp is a TEXT value equivalent to datetime('now') which returns an ISO formatted datetime string in UTC (-MM-DD HH:MM:SS). -Ursprüngliche Nachricht- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftra

[sqlite] one to one relationships

2 tables keyed alike are in a one to one relationship. IE every record of T1 will yield one and only one record in T2 PAUL ALAGNA pjala...@gmail.com ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http:

Re: [sqlite] [EXTERNAL] xRowid and read only virtual tables....

In our virtual table implementations, we are using the rowid to return the location of the record in the backing store (e.g. record offset in the file used as a backing store, offset within a shared memory section or maybe even the memory address of the record image) and also implement fast look

[sqlite] current_timestamp locale

Does SQLite go by users locale to insert date/time information into a row, or is it a very specific format when using current_timestamp as a default value? I don't want to go start monkeying with my system settings to find out, so, relying on those with experience. Thanks

Re: [sqlite] Sqlite3.6 Command-line delete/update not working with large db file(>280GB)

>>The setting for synchronous is basically what level of safety net do you want if it dies in the middle of something. Setting it to off shouldn't cause any corruption if things go well, it should only come into play if you saw errors or didn't close things down correctly etc. You're right, my Py

[sqlite] xRowid and read only virtual tables....

Hi, I am building a system which involves a number of virtual table implementations. They are all read-only, but will be involved in a bunch of joins amongst themselves. My question is this: the documentation http://sqlite.org/vtab.html#tabfunc2 at 2.12 xRowid seems (to my reading) to be alwa

Re: [sqlite] Sqlite3.6 Command-line delete/update not working with large db file(>280GB)

On Sun, 15 Oct 2017 18:36:56 -0700 (MST), Fiona wrote: > Thanks for noticing that problem! Follow your instructions, now I'm sure > it's all because my db file is corrupted. Is there anything I can do to fix > it? > > Integrity check result: >

Re: [sqlite] SQLite3 on Windows

On Sat, Oct 14, 2017 at 10:47 PM, Phoenix wrote: > Dominique wrote: > Not to sound too snarky, but both questions can easily be answered > through experimentation. > You can also use http://www.dependencywalker.com/ to inspect DLL and > EXE dependencies. --DD > > It's a bit difficult to d

Re: [sqlite] Sqlite3.6 Command-line delete/update not working with large db file(>280GB)

On 10/16/17, David Raymond wrote: > The setting for synchronous is basically what level of safety net do you > want if it dies in the middle of something. Setting it to off shouldn't > cause any corruption if things go well, it should only come into play if you > saw errors or didn't close things

Re: [sqlite] Sqlite3.6 Command-line delete/update not working with large db file(>280GB)

The setting for synchronous is basically what level of safety net do you want if it dies in the middle of something. Setting it to off shouldn't cause any corruption if things go well, it should only come into play if you saw errors or didn't close things down correctly etc. The unique index yo

Re: [sqlite] Using .testcase and .check in continuous integration test

On Mon, Oct 16, 2017 at 12:32 PM, Lodewijk Duymaer van Twist < lodew...@adesys.nl> wrote: > I would like use .testcase and .check in our GitLab Continuous Integration > test. > > GitLab pipelines will check process return code for success or fail. > > Consider a simple test: > lodewijk@DebianDev:~

[sqlite] Using .testcase and .check in continuous integration test

I would like use .testcase and .check in our GitLab Continuous Integration test. GitLab pipelines will check process return code for success or fail. Consider a simple test: lodewijk@DebianDev:~$ sqlite3 database.db3 < test.sql testcase-100 ok testcase-110 ok lodewijk@DebianDev:~$ echo $?

Re: [sqlite] Odd query plan for without rowid table

On Mon, Oct 16, 2017 at 12:28 AM, Richard Hipp wrote: > > Fixed on trunk. https://sqlite.org/src/info/ee31c043 FYI, small typo in that commit. --DD line 1885 of where.c ** Return TRUE if all of the following are true: ** ** (1) X has the same or lower cost that Y ** (2) X users fewer WHER