Cool! Thanks, glad it was not my problem, and glad it was fixed so fast.
On 6/12/2018 12:50 AM, Dan Kennedy wrote:
On 12/03/2018 10:37 AM, Philip Warner wrote:
Tables with complex triggers (possibly limited to "Insert...With",
though that is not clear), fail with &quo
Tables with complex triggers (possibly limited to "Insert...With", though
that is not clear), fail with "no such table".
The following produces the error in 3.26; a much simpler trigger does not
produce the error.
|Create Table LOG_ENTRY(||
|| LOG_ENTRY_ID int primary key,||
|| TIME
On 26/10/2018 11:02 PM, Gary R. Schmidt wrote:
On 26/10/2018 14:12, Philip Warner wrote:
I agree with the humour. As a satirical statement on the horrors of building
a good CoC/CoE it is quite effective.
But...if it is a CoC/E, then I think it would be beneficial to have one that
many
On 25/10/2018 9:59 PM, Mike King wrote:
I’m a good atheist but I love the CoC. Not bothered by the religious bits
but I get the sentiment. I guess it appeals to my British sense of irony
and odd sense of humour :)
I agree with the humour. As a satirical statement on the horrors of building a
On 25/10/2018 11:06 AM, Simon Slavin wrote:
The second exhortation tells us that that's not enough, and we also have a duty
to maximise pleasure.
lol, good point. Quite the opposite of monkish orders.
___
sqlite-users mailing list
sqlite-users@maili
On 25/10/2018 2:17 AM, Jens Alfke wrote:
Vague blanket statements like “Don’t be evil” or “Be excellent to each other”
don’t work (here or anywhere else.)
This is a good point. But it leads to the question: have you ever seen one that
works better than, say, "Don't be an arsehole/dick/evil"?
On 25/10/2018 9:11 AM, Richard Hipp wrote:
If you read the original CoC closely, you will find things that
required me to change it. We have:
18. Be a help in times of trouble
19. Console the sorrowing
31. Love your enemies
34. Be not proud
71. Make peace with your adversary befo
I'm guessing this is an appropriately satirical response to a ridiculous request
from corporates. If not, then:
- ditch all the religious mumbo-jumbo: 1, 10, 21, 41, 42, 44, 45, 46, 49, 50,
58, 60, 61, 62, 63, 70, 72
- and probably the masochism: 11
- and probably "Do not swear, for fear of
Interesting idea; when I've finished diagnosing my current problem, it might be
worth expanding the repertoire of the Android library.
I presume that the sqlite logging function could be used to get the message at
least, is that correct? IIRC, it's called on an error and the OS file-related
er
Not full, several gb free.
Will turn on logging and hope it plays well with Android.
Is it likely to be a threading issue? If so, will the logging show other
accesses to the file?
On 7 May 2017 2:13:28 am AEST, Dan Kennedy wrote:
>On 05/06/2017 02:13 PM, Philip Warner wrote:
>>
I have an Android app that does work in the database every five minutes (at
least). Every few days I am seeing:
org.sqlite.database.sqlite.SQLiteDiskIOException: disk I/O error (code 1034)
Code 1034 is SQLITE_IOERR_FSYNC.
This is using a custom build of the Sqlite bindings but I should not
Have sent a patch file direct to you (Dan).
On 21/04/2017 1:43 AM, Dan Kennedy wrote:
Sure, that sounds great! I don't think there are any license issues, as all
that code inherits the Apache 2.0 license from Android.
Are you fossil-literate?
___
On 21/04/2017 1:43 AM, Dan Kennedy wrote:
Are you fossil-literate?
Primarily git literate (cvs years ago). Happy to work my way through it.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mail
ns in terms of number of
devices that are live.
If I tidy up the code, do you have any interest in incorporating it, perhaps as
another branch?
On 20/04/2017 3:38 AM, Dan Kennedy wrote:
On 04/19/2017 06:28 PM, Philip Warner wrote:
FWIW, it compiles and builds with API set to 14...I'm ju
There is another reason to have stored procedures: encapsulating logic across
apps/clients.
A great deal can be done in triggers, but not much in terms of queries or
complex parameterized updates.
It would be great, imo, if triggers could have durable local storage (ie.
variables) and if thi
FWIW, it compiles and builds with API set to 14...I'm just worried I'll get some
esoteric breakage.
Any insights from someone who understands NDK/API level interactions?
On 18/04/2017 11:49 PM, Philip Warner wrote:
I notice that the Android bindings support API 16 by default, wit
I notice that the Android bindings support API 16 by default, with a custom
branch for API 15. Naively, it looks like API 15 support has a small number of
changes relating to a missing/changed(?) exception.
Can anyone offer insight into how difficult it would be to support API 14 or
below? It d
On 2/11/2015 1:49 AM, Gerald Bauer wrote:
>I've started a new project, that is, /factbook.sql [1] that offers
> an SQL schema for the World Factbook and also includes a pre-built
> single-file SQLite database, that is, factbook.db [2] for download.
Have you seen the XML/mysql versoin:
ht
Just came back to check on this, but there were no replies.
Is there a better contact for the ICU extensions?
On 14/04/2015 2:43 PM, Philip Warner wrote:
> I've been using SqlCipher (built locally with ICU extensions) and can do the
> following:
>
> sqlite> selec
I've been using SqlCipher (built locally with ICU extensions) and can do the
following:
sqlite> select icu_load_collation('[][][]','q');
sqlite> select * from foo order by f1 collate q;
Which worries me.
I assume this is an Sqlite+ICU problem.
Does anyone have any insights into what is going o
On 9/01/2015 5:00 PM, Dan Kennedy wrote:
On 01/08/2015 07:48 AM, Philip Warner wrote:
How difficult would it be to add LOCALIZED collation support? I'm guessing
that the fact it's not there means it's non-trivial, but I was hoping
otherwise...
The stumbling block is t
I just saw the SQLite Android Bindings page at
http://www.sqlite.org/android/doc/trunk/www/index.wiki
but was a little disappointed to read in the details that UNICODE and LOCALIZED
are not supported. I'd really like the latest SQLite, and LOCALIZED.
How difficult would it be to add LOCAL
Native UNICODE?
Dates? UUID (stored as bytes, displayed as string)? I know...new data type
representations are unlikely.
Triggers with declared variables that are preserved across invocations?
(...using temp tables is a pita for storing, say, 5 numbers)
___
On 6/03/2013 1:59 AM, Jay A. Kreibich wrote:
> In this case, it is any trigger that invokes any other trigger.
> Prior to 3.6.18 there was no trigger "stack" and triggers could be
> only one layer deep.
Ah, thanks. That solves the problem. I can dynamically generate a single
inefficient trigg
On 5/03/2013 9:53 PM, Richard Hipp wrote:
> Recursive triggers (triggers that invoke themselves either directly or
> indirectly) were added in version 3.6.18, 2009-09-11.
These are not strictly recursive; the 'when' clause means that trigger 1 will
cause trigger 2 to be called etc.
_
This is a question about triggers in version 3.5.9...if anyone remembers it.
The reason I am asking is that I want to support
Android 2.1, which has 3.5.9 installed by default.
I have a set of triggers on a table:
tg1 before insert on sometable when new.f1 = 3
insert into sometable(f1, ...)
John Machin wrote:
> Assuming your guid is a BLOB, then
>SELECT other_stuff, QUOTE(guid), etc
> will display it as hex e.g. X'01020304'
>
This is great; now I can see them at least!
>> P.S. Of course even better would be the ability to read/write GUIDs as
>> properly formatted strings! (Not
here any
simple way (or just a hack) that I could persuade the shell to output
GUIDs (or all binary data) in the same format as for .dump?
Thanks,
Philip Warner
P.S. Of course even better would be the ability to read/write GUIDs as
properly formatted strings! (Note: I am not asking that
28 matches
Mail list logo
