Hello!

after a long time i came back to have a look at sqlite again. As a sql
database running on Linux and Windows without additional installation
required (just packaging the other tcl stuff and running out of the box)
it is totally fullfilling my needs.

I assume it is running at SunOS, HP-UX and BSD systems too, isn't it?

Are there any performance issues comparing 2.8.15 and 3.0.4?

By the way i get an communication error downloading
tclsqlite-3.0.4.so.gz, and there seems to be no tcl binding at
tclsqlite-3.0.3.so.gz.

-------

question 1: is there a way to handle read and write access differently? 

note: using msql2/3 so far, i want to create demo versions of my
applications using sqlite instead. Many of this applications have
generic sql interfaces. They are used very often. Using this interface
there are two different rights:

1. read access: selection of data is allowed
2. read/write access: changing/removing of data is allowed additionally,
creating/deleting/indexing tables 

At msql2/3 there was a simple way to achieve this: msqlsel was only able
to get data and msqlexec is able to execute arbitrary sql statements

Is there a way to do this similar using "$sqllite_handle eval args" like
a switch -readonly or -readwrite

-------

question 2: the eval method allows to execute several comma seperated
sql statements at once. Are there any performance issues? How many bulks
are optimal for different operating systems?

note: i tested this just once comparing 60000 single statements and a
bulk insert of 60000 statements. The later took about twice in time.

-------

question 2: sqlite requires unique table/index name per database? Is
this standard? 

example: second table can not be created as index has the same name

CREATE TABLE sg (
  loc CHAR(20)
) ;

CREATE INDEX sg_LBD ON sg (
        loc
) ;


CREATE TABLE sg_LBD (
  loc CHAR(20)
) ;

CREATE INDEX sg_LBD ON sg_LBD (
        loc
) ;

stderr: there is already an index named sg_LBD

and 

stderr: index sg_LBD already exists

fix: simple; change definitions at runtime, e.g. use tablename as prefix
and a unique id
    

-------

question 4: how to esacpe ' characters? 
          (thought sql required \\ and \' or is this msql1/2/3
specific?)

example: 

INSERT INTO sg  VALUES ('two quotes '' are recognized');

INSERT INTO sg  VALUES ('this doesn\'t work');

stderr: near "s": syntax error

fix: simple; insert layer to handle escape per database system, convert
data at change

-------

question 5:  table fields can not be named 'Group' or 'check'?
           (as used in msql1/2/3 so far)

fix: hard; rename/restructure existing data fields in database and
applications

------

TIA

Stefan
 
__________________________________________________________

  Stefan G. R. Finzel      Dipl. Phys. (Univ.)
  Ochsenkopfstraße 5       Phone +49 (0)9642 704448
  D - 95478 Kemnath        [EMAIL PROTECTED]
  Germany, Europe          http://www.osn.de/user/finzel
__________________________________________________________

Reply via email to