Thank you for the release!
I can't find sqlite-shell-linux-x86-3071501.zip and sqlite-doc-3071501.zip.
On 12/19/2012 10:24 PM, D. Richard Hipp wrote:
> SQLite version 3.7.15.1, a patch release, is now available on the SQLite
> website:
>
> http://www.sqlite.org/
>
> This patch release
On Wed, 19 Dec 2012 21:10:28 -0500, Richard Hipp wrote:
> The latest SQLite from trunk (not the 3.7.15.1 patch release,
> but the code that is destined to become 3.7.16) has a new pragma:
>
>PRAGMA foreign_key_check;
>PRAGMA foreign_key_check(TABLE);
>
> The second from
On Wed, Dec 12, 2012 at 2:29 PM, Levi Haskell (BLOOMBERG/ 731 LEXIN) <
lhask...@bloomberg.net> wrote:
> My suggestion would be to have check_integrity command verify referential
> integrity as well only if it's executed while the foreign key enforcement
> is enabled on the connection.
>
The
SQLite version 3.7.15.1, a patch release, is now available on the SQLite
website:
http://www.sqlite.org/
This patch release fixes a single bug the managed to sneak into the 3.7.15
release from last week. Two lines of code changed and one assert() was added:
Igor
>case when f.nexttime IS NOT NULL then 0 else 1 end
explains it very well and I see that your alternative is indeed an elegant
shortcut
Additionally...
thank you for putting me straight re NULL in SQL
I didn;t appreciate that
Your help is very much appreciated
Dean
On 19 December 2012
On 12/19/2012 10:07 AM, e-mail mgbg25171 wrote:
Given this I fully understand Ordering by that which I require i.e.
non-null...non empty string and the latter of the above does precisely that
i.e. when nexttime is not null then 0... and... when lasttime is not null
BY CONTRAST the first query
On Wed, Dec 19, 2012 at 12:00 PM, wrote:
> Re: Suggested Improvement of Date Time Function (Larry Brasfield)
We currently store timestamps in this javams integer format which
allows millisecond precision in a fixed 13 character/digit space.
Our usage may not be
Somebody claiming to be "IQ Support Team" wrote:
Suggesting addition of two new modifiers to SQLITE Date Time functions.
Add new modifier(14):javams and modifier(15):javanano similar to
unixepoch modifier but extended to support milliseconds and
nanoseconds.
This seems like an
Thank you for the principal.
I had to rewrite a little since I only wanted to affect the rows that
were using the max entry.
Adam
On Tue, Dec 18, 2012 at 12:58 PM, Igor Tandetnik wrote:
> On 12/18/2012 12:27 PM, Adam DeVita wrote:
>>
>> There is a table products where has a
Thank Igor
Again...your solution works a treat...
Re my confusion...please contrast these two which both work
i.e.
order by (f.nexttime is null or f.nexttime=''), coalesce(f.nexttime, ''),
f.lastdate
vs
order by (case
when nexttime is not null then 0
when lasttime is not null then 1
Suggesting addition of two new modifiers to SQLITE Date Time functions.
Add new modifier(14):javams and modifier(15):javanano similar to
unixepoch modifier but extended to support milliseconds and
nanoseconds.
The "javams" modifier (14) only works if it immediately follows a
timestring in the
e-mail mgbg25171 wrote:
>> order by (f.nexttime is null or f.nexttime=''), coalesce(f.nexttime,
>> ''),f.lastdate
>
> This worked fine re making sure that non-null nexttimes come BEFORE null
> nexttimes.
>
> How would I extend this so that AFTER non-null nexttimes I
tigeryth wrote:
i used CDaoRecordset of MFC to handle records in ACCESS, whick is convenient to
me move around records in table and edit certain record.
according to my habit, i wish sqlite has some kind of functions like, move(int)
to get to cerctain record, getbookmark(...) to the record
On 18 Dec 2012, at 3:03pm, tigeryth wrote:
> i use sqlite in my project. it is good because of its capacity bigger than
> ACCESS. i used CDaoRecordset of MFC to handle records in ACCESS, whick is
> convenient to me move around records in table and edit certain record.
>
hi,
i use sqlite in my project. it is good because of its capacity bigger than
ACCESS. i used CDaoRecordset of MFC to handle records in ACCESS, whick is
convenient to me move around records in table and edit certain record.
according to my habit, i wish sqlite has some kind of functions
>order by (f.nexttime is null or f.nexttime=''), coalesce(f.nexttime,
''),f.lastdate
This worked fine re making sure that non-null nexttimes come BEFORE null
nexttimes.
How would I extend this so that AFTER non-null nexttimes I get NON-NULL
lasttimes and then...
null nexttimes and lastimes in
16 matches
Mail list logo