Re: forms and native SQL

Moin Oliver,

On 11.11.2010 23:52, Oliver Peters wrote:
> Hello,
>
> I'm working with sqlite 3.7.3 as an external db via ODBC
> (http://www.ch-werner.de/sqliteodbc/) under WinXP.
>
> My frontend is OOo Base (330 RC4). For inserting and updating tables I
> use forms. If I choose SQL as a datasource for the form and don't allow
> OOo to check the SQL (because I use sqlite specific constructs) I can't
> insert or update anymore. The same with "ordinary" queries. I feel(!)
> that this is a wanted behaviour that is reproducable with other dbs
> (PostgreSQL, MySQL,...) but I can't explain why this should be
> necessary.
>
> Any hints/coaching are/is appreciated.
The reason is that we need to uniquely identify a row. This is done by 
fetching the primary key column(s). When we now can't parse the SQL 
statement how should we know that all primary key column(s) are part of 
the select. And how they are named. As work around I would try to 
convert the sqlite specific constructs to standard SQL where possible.

Best regards,

Ocke
>
> Oliver
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>