Re: [sqlite] German umlauts (äöüß) are not displayed in sqlite - solution

[A. Klitzing]

Wolfgang Qual schrieb:
> Hi Markus,
> thanks for this hint. Using an editor, I saw that the "Umlauts" are there.
> But is there a way to make the Umlauts visible also on the 
> sqlite-commandline/sqlitebrowser (for select-statements necessary)?
> 
> Best regards,
> Wolfgang


Hello,

you can try SQLite Spy [1] for that. It shows Unicode-Chars correctly.

[1] http://www.yunqa.de/delphi/sqlitespy/

Regards,
A. Klitzing



signature.asc
Description: OpenPGP digital signature

Re: [sqlite] Prepared statements and temp ffiles

[A. Klitzing]

Jay Sprenkle schrieb:

On 9/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:


The only way I know to provide some approximation of random
access cursors for queries like the above is to store the
complete result of the query in a temporary table.  You can
always do so by prepending:


Did anyone suggest doing that to them? It seems a simple matter
to select the unique keys from the set you want and cache them.


What do you mean? That's the same problem like above. ;-)

There is no problem to cache the querys and get information from it. The 
problem is that it will take A LOT of ressources to get the information.
After EVERY call for information you must close the query to the 
resultset (and OOo will call many functions).
OOo has more than one window and maybe a user wants to create/drop a 
table while he is watching another table. So you need to close your temp 
table-query or he won't be able to create/drop his tables.


There is no problem to have the resultset in a temp table.
I think we will use a cache for a cache now to avoid massive 
SELECT-usage... that isn't pretty but it will work.


Temp Tables are in separate files... so I hope it will be possible 
someday to drop/create tables in the main-database while one cursor is 
pending on the temp-table. ;-)


Regards,
André Klitzing



signature.asc
Description: OpenPGP digital signature

Re: [sqlite] Prepared statements and temp ffiles

[A. Klitzing]

Now if you follow this strategy, notice that you never need
to keep pending read operations around.  The original query
builds the temp table in a single sqlite3_step() call.  To
access the results, you prepare a statement like this:

 SELECT * FROM result_set_1 WHERE rowid=?



Of course you don't need any pending cursors. But the problem is that 
OOo will call many functions for only one row to get informations. I 
tested that way and I got a 10 times slower run duration with that. If I 
can use an open stmt it will be fast because I don't need to run SELECT 
more than once for one cursor-movement in the resultset.


If we have a table with 10.000 rows, 5 columns and one column is a 
primary key.
OOo will SELECT * to get primary keys. After that it will use new SELECT 
for EVERY single row to get the type and the content. And of course it 
will get the content and type for every cell.


So you will have 50.001 SELECT-stmt only to get same information because 
I can't remember my cursor-position.



Regards,
André Klitzing



signature.asc
Description: OpenPGP digital signature

[sqlite] Re: sqlite3_step() vs. get_tables() - CPU-Usage

[A. Klitzing]

Thanks, I think I will write my own 'cache' with sqlite3_step().



signature.asc
Description: OpenPGP digital signature

[sqlite] sqlite3_step() vs. get_tables() - CPU-Usage

[A. Klitzing]

Hello,

I need some information about the sqlite3_step() function.
How much CPU-usage does it need in comparison with sqlite3_get_tables()?

I have to implement functions like next(), prev(), last(), first(), 
relative(int) and absolute(int).


#1 Way - sqlite3_step()
I can only step forward with sqlite3_step() and use sqlite3_reset() to get 
first() and iterate through the result to the position for relative() and so on.

#2 Way - sqlite3_get_tables()
I can use get_tables() instead and so I can set my cursor without problems to 
every relative position but I loose nice features that I have with sqlite3_stmt.


So the question is - needs sqlite3_step() a few performance so it is "ok" that 
I will iterate "dirty" through the result everytime?

Regards,
André Klitzing

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

[sqlite] SQLite 2.8.17 - Interface

[A. Klitzing]

Hello,

I just wanted to ask if there is an interface change from version 2.8.16 
to 2.8.17?


Because I need to know it for Ubuntu Dapper.
https://launchpad.net/distros/ubuntu/+source/sqlite/+bug/36732


Thanks,
A. Klitzing