Re: [sqlite] Features of SQLite question

On Mon, Jun 11, 2012 at 10:11:45PM +, Black, Michael (IS) scratched on the wall: > Answer: The most recent one. > > Isn't it true that semi-accurate (sub-second) time-tagged transactions > will generally keep 2 databases in sync? "Generally", perhaps, but not always. > I've done that

Re: [sqlite] Features of SQLite question

On 12 Jun 2012, at 12:06am, Brent Shifley wrote: > So, if I understand things correctly, if I created said app, with associated > database, if I had identical databases on both iPads, and tracked all > transactions and used them to modify a third copy of the database,

Re: [sqlite] Features of SQLite question

Wow! I feel I just tried to eat an elephant. ;) What I am thinking of doing is creating a specialized app for handling contacts related to a business that I own. I am formerly a software tester that was exposed to a lot of different things, including a little sql. Now, back to the

Re: [sqlite] Features of SQLite question

On 11 Jun 2012, at 11:11pm, "Black, Michael (IS)" wrote: > Isn't it true that semi-accurate (sub-second) time-tagged transactions will > generally keep 2 databases in sync? > > I've done that before with considerable success. You don't sync the > fields...you sync

Re: [sqlite] Features of SQLite question

Answer: The most recent one. Isn't it true that semi-accurate (sub-second) time-tagged transactions will generally keep 2 databases in sync? I've done that before with considerable success. You don't sync the fields...you sync the transactions. The presumption is that later transactions

Re: [sqlite] Features of SQLite question

On 11 Jun 2012, at 10:14pm, Brent Shifley wrote: > I was wondering. If you had a SQLite database on two different iPads, then > had different changes applied to each database, is it possible to sync the > changes to each database? Suppose you have a list of contacts

Re: [sqlite] Features of SQLite question

On Mon, Jun 11, 2012 at 04:14:59PM -0500, Brent Shifley scratched on the wall: > I was wondering. If you had a SQLite database on two different iPads, > then had different changes applied to each database, is it possible to > sync the changes to each database? Sure, why not? Does SQLite

[sqlite] Features of SQLite question

I was wondering. If you had a SQLite database on two different iPads, then had different changes applied to each database, is it possible to sync the changes to each database? Sent from my iPad ___ sqlite-users mailing list sqlite-users@sqlite.org

Re: [sqlite] Quoting "id" versus 'id' in query

> You have overstated the requirements upon SQL identifiers.  Quoting via > surrounding double-quote is only necessary if the identifier would not meet > the definition of a "regular identifier", loosely understood to be a letter > followed by letter, digit or underscore characters. Also quoting

Re: [sqlite] Quoting "id" versus 'id' in query

On June 11, rick wrote: Yes, it can be explained: says: 'keyword' A keyword in single quotes is a string literal. "keyword" A keyword in double-quotes is an identifier So, "id" is interpreted as a column name, not as the string literal 'id', unless

Re: [sqlite] Quoting "id" versus 'id' in query

On June 11, rick wrote: Something I noticed today: sqlite> select * FROM words WHERE word = "id"; sqlite> select * FROM words WHERE word = 'id'; 13556|id sqlite> .schema CREATE TABLE words ( id integer primary key, word varchar(64) ); Yes, it can be explained:

[sqlite] Quoting "id" versus 'id' in query

Something I noticed today: sqlite> select * FROM words WHERE word = "id"; sqlite> select * FROM words WHERE word = 'id'; 13556|id sqlite> .schema CREATE TABLE words ( id integer primary key, word varchar(64) ); Yes, it can be explained:

Re: [sqlite] Running SQLite Test Suites

> The "test" target is in the file "main.mk" which is "include"-ed by the very > last line of Makefile.linux-gcc. Thanks Richard. That clears up things. -- Grace Batumbya Research Assistant | Seneca CDOT Phone: 416-491-5050 x3548 cdot.senecac.on.ca

Re: [sqlite] Running SQLite Test Suites

The "test" target is in the file "main.mk" which is "include"-ed by the very last line of Makefile.linux-gcc. On Mon, Jun 11, 2012 at 1:33 PM, Grace Batumbya < grace.batum...@senecacollege.ca> wrote: > >./configure; make test > > > > > >I just ran it on Solaris, as shown above, and it appears to

Re: [sqlite] Specifying a nullable column

On Mon, Jun 11, 2012 at 10:35 AM, Paul Medynski wrote: > Hi folks, > > I notice that the syntax diagram for 'create table' shows the > 'column-constraint' definition as requiring 'null' to always be preceded by > 'not'. I don't see any definition that supports just 'null'.

Re: [sqlite] Running SQLite Test Suites

>./configure; make test > >I just ran it on Solaris, as shown above, and it appears to be working fine. >You will need a relatively recent version of TCL, however. 8.5 or 8.6. >From the REAME file: ... If the configure script does not work out for you, there is a generic makefile named

Re: [sqlite] integrity constraint that is equivalent to the following trigger:

Am 10.06.12 14:59, schrieb Petite Abeille: > > The short of it is that you can't. SQLite doesn't support such constraints. > Only the basics are supported: primary, unique, referential, not null, check: > Thank you for that information. It saves me a lot of time searching for a solution that

[sqlite] Specifying a nullable column

Hi folks, I notice that the syntax diagram for 'create table' shows the 'column-constraint' definition as requiring 'null' to always be preceded by 'not'. I don't see any definition that supports just 'null'. However, when using SQLite3 3.7.3 or 3.7.9, I can create a table and specify any

Re: [sqlite] .nullvalue

On 11 Jun 2012, at 9:47am, Klaas Van Be wrote: > We're supposed to be able to change the representation of the NULL value. > Whatever parameter I choose it does not seem to work. I always get an empty > string. I think you have empty strings in the table, and that's why

[sqlite] .nullvalue

Ciao fellow SQLite users, We're supposed to be able to change the representation of the NULL value. Whatever parameter I choose it does not seem to work. I always get an empty string. What I did wrong in this sample table, the commands or parameters? sqlite> .nullvalue * sqlite> select