Any particular reason why the shell '.import' command cannot interpret ||
as a NULL for the field?
Does || have another use/interpretation?
Just seems a shame that the standard bulk input mechanism cannot cope
directly with NULLs.
Best regards
On Wed, Mar 16, 2016 at 9:13 AM, Simon Slavin wrote
I couldn't find this issue documented anywhere.
If it is required to import NULL values into an Sqlite table field, can
this be done simply by arranging that the before and after delimiters for
that field are consecutive?
Example: For a three field table (all three fields text type), importing
fr
y to the OS, then SQLITE_OK will only be
returned after a transaction is irreversably fixed on the disk?
Best regards
On Sat, Feb 6, 2016 at 2:45 PM, Richard Hipp wrote:
> On 2/6/16, Bernard McNeill wrote:
> > Please can I formally propose that, for Linux:
> > 1. A Pragma or
Please can I formally propose that, for Linux:
1. A Pragma or other compile-time option is created such that SQLITE_OK is
not issued on file writes/modifications/deletes until the hardware
indicates that all associated Directory syncs, etc., are done.
2. Since the absence of 1. appears to break the
es, needed
under Linux?
(I appreciate the disk hard/firmware will need to be looked at as well)
Best regards
On Thu, Jan 28, 2016 at 4:37 PM, Howard Chu wrote:
> Simon Slavin wrote:
>
>>
>> On 28 Jan 2016, at 1:38pm, Bernard McNeill wrote:
>>
>> ===
>>> Li
===
Like the user reading ?saving OK? and throwing away the
Post-It with the original information
===
This is exactly my concern.
The user throwing away the Post-It is entirely reasonable if he sees a
message like that.
Do you happen to know if Linux/Debian (which I think uses a journalling
files
Just to be clear
Situation: Under Linux/Debian, Sqlite opens an entirely valid DB, and runs
an entirely valid SQL transaction against that database.
Following a Commit, the application gets back a 'Commit Successful' code.
(Ignore any issues of disks returning hardware 'write done' flags
premature
Hello,
Anyone with any experiences with this (good or bad)?
Idea to have Sqlite database on server, accessed from a few ultra-thin
Terminal clients.
Best regards
8 matches
Mail list logo
