Re: [sqlite] Helping with table definition?

Hi, I think you should look at "PRAGMA table_info(table-name);" instead: For each column in the named table, invoke the callback function once with information about that column, including the column name, data type, whether or not the column can be NULL, and the default value for the column.

RE: [sqlite] Helping with table definition?

This is code I used a while ago. Don't use it anymore as I have a better way to do this via my VB wrapper. There are some lines that deal with code in other parts of my application, but I take it you can see that. In case you didn't know this is VB(A). Function GetSQLiteTableInfo2(strDB As

[sqlite] Sqlite - Latino America

Hello Community Sqlite We Gerardo Antonio Cabero and Daniel Maldonado, administrators Sqlite http://sqlite-latino.blogspot.com/ Latin America -- Sqlite Latin America? A site for the communities of Sqlite Hablahispana, which are available examples, documentation We are the Latino community sqlite .

[sqlite] Fastest way to check if new row or update existing one?

hi, just a short question to speed up: as with any database one has quite often to decide if we *INSERT a NEW row -- or -- UPDATE an existing row* at the moment I do a check select on an unique ID intege which is resonable fast: code:

[sqlite] Re: Fastest way to check if new row or update existing one?

* Mag. Wilhelm Braun <[EMAIL PROTECTED]> [2007-12-25 15:10]: > QUESTION: is there a better way to make this important > decision? using Sqlite 1. If you are changing the entire row on every update, you can simply use `INSERT OR REPLACE` (assuming there is a UNIQUE column) to always do this

Re: [sqlite] Fastest way to check if new row or update existing one?

On Tue, 25 Dec 2007 15:07:12 +0100, "Mag. Wilhelm Braun" <[EMAIL PROTECTED]> wrote: >hi, > >just a short question to speed up: > >as with any database one has quite often to decide if we *INSERT a NEW >row -- or -- UPDATE an existing row* > > >at the moment I do a check select on an unique ID

Re: [sqlite] Helping with table definition?

Cesar D. Rodas wrote: Hello, Merry Christmas for every one! I am wondering if someone did a function (the language doesn't care very much) to get the table information and want to share him/her code. Here's some Tcl code that may help. It does more than look at the SQL, but that part may

Re: [sqlite] Re: Fastest way to check if new row or update existing one?

Thanks as in my case just number 2 is possible a quite 'silly' question: How do you normally check if Update was successful if the specified row did not exists. e.g: UPDATE MyTable SET Account='MyAccountName' WHERE ID=50 If row 50 does not exists it does nothing and I seem not to get any

Re: [sqlite] Re: Fastest way to check if new row or update existing one?

On Tue, 25 Dec 2007 19:24:48 +0100, "Mag. Wilhelm Braun" <[EMAIL PROTECTED]> wrote: >Thanks as in my case just number 2 is possible a quite 'silly' question: >How do you normally check if Update was successful if the specified row >did not exists. > >e.g: UPDATE MyTable SET

Re: [sqlite] Re: Fastest way to check if new row or update existing one?

Thanks Pagaltzis. Great help. W.Braun A. Pagaltzis wrote: * Mag. Wilhelm Braun <[EMAIL PROTECTED]> [2007-12-25 19:30]: If row 50 does not exists it does nothing and I seem not to get any return to know? http://sqlite.org/c3ref/changes.html using pysqlite. I don’t know

[sqlite] Re: Fastest way to check if new row or update existing one?

* Mag. Wilhelm Braun <[EMAIL PROTECTED]> [2007-12-25 19:30]: > If row 50 does not exists it does nothing and I seem not to get > any return to know? http://sqlite.org/c3ref/changes.html > using pysqlite. I don’t know anything about pysqlite, but apparently you are looking for the `rowcount`

[sqlite] disable transaction support

Hi All, I have an application which inserts large number of rows into a table, where transaction support is not necessary. For performance reason, i need to disable the transaction support in sqlite version 3.3.17 . How can i do it? any help is highly appreciated. -- Thanks, Rasanth

[sqlite] PySQLite problem

Hello, I was testing PySQLite and got an exception: Traceback (most recent call last): File "D:\code.cesarodas.com\etopa\test2.py", line 33, in for result in search(raw_input("Search:")): File "D:\code.cesarodas.com\etopa\files.py", line 147, in search r = cu.execute('select dir,

Re: [sqlite] disable transaction support

On the contrary, sqlite work much-much faster when insert/update is done within BEGIN and COMMIT; regards, Radzi. On 26-Dec-2007, at 12:14 PM, Rasanth Akali Kandoth wrote: Hi All, I have an application which inserts large number of rows into a table, where transaction support is not

Re: [sqlite] disable transaction support

Hi Radzi, i do it with BEGIN and COMMIT. it is that, even in this case for transaction support sqlite has to write into the journal files as well. i want to avoid this too. Thanks, Rasanth On Dec 26, 2007 11:34 AM, Mohd Radzi Ibrahim <[EMAIL PROTECTED]> wrote: > On the contrary, sqlite work

Re: [sqlite] disable transaction support

Hi Rasanth, I'm not an expert in SQLite. Not sure what kind of performance gain you want to achieve. Perhaps you could try "pragma synchronous=off". Or in-memory database... I guess the journal is there to provide ACID db characteristic. For me even with that out-of-the-box, the insert

Re: [sqlite] disable transaction support

The fastest performance you will get is with synchronous off. That will relax the ACID requirement on the COMMIT but it can be unsafe if you get a crash during the commit. Mohd Radzi Ibrahim wrote: Hi Rasanth, I'm not an expert in SQLite. Not sure what kind of performance gain you want to