Re: [sqlite] Converting Sqlite to Myqsl

- Forwarded by Ben Carlyle/AU/IRSA/Rail on 22/01/2004 11:13 AM - Ben Carlyle 22/01/2004 11:06 AM To: Martin Brinkmann <[EMAIL PROTECTED]>@CORP cc: Subject:Re: [sqlite] Converting Sqlite to Myqsl Martin, Martin Brinkmann <[EMAIL PROTECTED]> 22/0

[sqlite] Converting Sqlite to Myqsl

Hello all, this is my first post, i know a little php and mysql. Iam also using a program which analyses ebay products. Unfortunatly it only exports the data i gather as a Sqlite 2.1 Database file with the extension filename.idb I tried to find a easy way of converting the file to mysql format,

Re: [sqlite] Update-Triggers on Views

> I have a view that left-joins two tables, where the first table has got unique > columns. I have created an insert-trigger and an update-trigger on the view. > The insert trigger works fine. > If I do an "UPDATE testview SET xyz='test' WHERE id=1;" the update-trigger > throws an error 'SQL error:

[sqlite] Update-Triggers on Views

Hi, I have a view that left-joins two tables, where the first table has got unique columns. I have created an insert-trigger and an update-trigger on the view. The insert trigger works fine. If I do an "UPDATE testview SET xyz='test' WHERE id=1;" the update-trigger throws an error 'SQL error: c

Re: [sqlite] Query problem

D. Richard Hipp wrote: Simon Berthiaume wrote: For those of you that tends to write complex queries, I noted that SQLite doesn't like when a table name follows a opening parenthesis in the FROM clause. The simplest fix for this would be to insert "SELECT * FROM" right after the "(" in the FROM

Re: [sqlite] Query problem

Simon Berthiaume wrote: For those of you that tends to write complex queries, I noted that SQLite doesn't like when a table name follows a opening parenthesis in the FROM clause. The simplest fix for this would be to insert "SELECT * FROM" right after the "(" in the FROM list. So, if the original

Re: [sqlite] Query problem

For those of you that tends to write complex queries, I noted that SQLite doesn't like when a table name follows a opening parenthesis in the FROM clause. For example, the following works under Access ans Oracle, but not in SQLite: SELECT T0.OBJECTS_ID , T0.OBJECTS_REFNO, T8.OBJECTS_LOCATION_LOCATI

Re: [sqlite] Performance...there must be a reason

Avner Levy wrote: I've downloaded the latest src and compiled the new version 2.8.11 on Solaris 2.8 and tried to check the lock fix with the threadtest1.c. The output was as followed: === 2.testdb-4: command fail

Re: [sqlite] Transaction -> OE_Ignore

Steven Van Ingelgem wrote: How do I set a transaction (inserting items) to ignore doubles in keys? As the default behaviour now is to abort/rollback... I've also been looking where the sqlite_vm - structure is defined, but I did not found anything... Is that normal? Or is it just a pointer to a

Re: [sqlite] basic table level stuff

On Wed, Jan 21, 2004 at 03:22:29AM -0500, jim wrote: > for some reason they are trying to name the constraint. no idea why. That determines the name of the index that will be used to implement the constraint. > It appears sqlitemanager doesn't use it. Yup, it looks like sqlite ignores the cons

RE: [sqlite] basic table level stuff

>>I am also wondering about the constraint in the column-def like column-def ::= name [type] [[CONSTRAINT name] column- >>constraint]* I thought about this some more. since constraint shows up in blue it is reserved. for some reason they are trying to name the constraint. no idea why. It appear

Re: [sqlite] Performance...there must be a reason

I've downloaded the latest src and compiled the new version 2.8.11 on Solaris 2.8 and tried to check the lock fix with the threadtest1.c. The output was as followed: === 1.testdb-1: START 2.testdb-1: START 1.testdb