Re: [sqlite] Are parenthesis really needed?

> the case. In general, LEFT OUTER JOIN is not commutative, nor is it > associative. You cannot blindy strip the parens or reorder the outer joins > out of context. > hmmm I see. Thanks for you attention, Joe. Regards, Bruno -- /** * Bruno S. Oliveira * Bacharel em Ciência da C

[sqlite] Are parenthesis really needed?

to remove every possible parenthesis present in the incoming query. So that my problem is resolved fast. Can I do that safely? Thanks in advance. Regards -- /** * Bruno S. Oliveira * Bacharel em Ciência da Computação - UFLA * Mestrando em Inteligência Computacional - UFPR * http

Re: [sqlite] Columns from nested joins aren't properly propagated

t; Bruno > > > > On 8/17/07, Joe Wilson <[EMAIL PROTECTED]> wrote: > > > SELECT t_dados.id > > > FROM Points1 LEFT JOIN t_dados ON Points1.object_id = t_dados.id > > > ORDER BY t_dados.id, Points1.geom_id; > > > > > > --- "Bruno

Re: [sqlite] Columns from nested joins aren't properly propagated

t_dados.id > ORDER BY t_dados.id, Points1.geom_id; > > --- "Bruno S. Oliveira" <[EMAIL PROTECTED]> wrote: > > I'm having problems with the following query (and, in general, in > > queries using left joins): > > > > [EMAIL PROTECTED]:~$ sqlite3 p

[sqlite] Columns from nested joins aren't properly propagated

w can I solve this? Will this issue be corrected in a near future SQLite update? Any hint will be pretty much appreciated. Thanks in advance. Best regards, Bruno -- /** * Bruno S. Oliveira * Bacharel em Ciência da Computação * Mestrando em Inteligência Computacional * http://www.inf.ufpr.br/brunoso/ * * http://www.last.fm/user/bsoliveira/ */

[sqlite] sqlite3_step

Hi all, I'm having problems with the sqlite3_step function. I have a table with only one record and then I execute the sqlite3_step twice (with some processing in between). In the first run of the function everything goes fine, but, in the second one, it returns SQLITE_ROW even with only one reco

Re: [sqlite] auto_increment and not null

Thanks Andrew and everyone. I'll see what I can get with it. Thanks for your attention, Bruno On 6/28/07, Andrew Finkenstadt <[EMAIL PROTECTED]> wrote: On 6/28/07, Bruno S. Oliveira <[EMAIL PROTECTED]> wrote: > > Hi all, > > Now I see the what's happening

Re: [sqlite] auto_increment and not null

Hi all, Now I see the what's happening. But what if I need to create a table with two primary keys and one auto incremented (and I DO need that!)? Isn't this possible? Thanks a lot Trevor and all. Thanks for the attention. Best regards, Bruno On 6/28/07, Trevor Talbot <[EMAIL PROTECTED]> wrot

Re: [sqlite] auto_increment and not null

Hi, On 6/28/07, Trevor Talbot <[EMAIL PROTECTED]> wrote: "integer primary key" is special, and the only column "autoincrement" can be applied to. It's not a general-purpose sequence option, like some other database engines. Yep, I knew that. The problem is that, with a table created like th

Re: [sqlite] auto_increment and not null

Hi Griggs and everyone, Nop, the problem isn't the underscore. The sqlite works with both keywords: AUTOINCREMENT and AUTO_INCREMENT. Thanks for the attention! Regards, Bruno On 6/28/07, Griggs, Donald <[EMAIL PROTECTED]> wrote: Regarding: "I'm aware of the create table syntax. And accordin

Re: [sqlite] auto_increment and not null

ion, Eugene. Best regards, Bruno http://www.sqlite.org/lang_createtable.html Regards, Eugene Wee Bruno S. Oliveira wrote: > Hi all, > > I'm having some trouble in inserting data into a table which its > primary key is set as auto_increment and not null. > The table was created as fo

[sqlite] auto_increment and not null

Hi all, I'm having some trouble in inserting data into a table which its primary key is set as auto_increment and not null. The table was created as follows: CREATE TABLE te_representation (repres_id INTEGER AUTO_INCREMENT NOT NULL ,layer_id INTEGER ,geom_type INTEGER ,geom_table TEXT ,desc