Asko Kauppi wrote:
Still, shouldn't the 'mri_output' (table name) be quoted?
17.2.2005 kello 11:45, Anirban Sarkar kirjoitti:
I am really very sorry.
I mistyped the entire sql statement. This is what my actual code looks like:
sqlite db1 "cesc_simputer.db"
#Inserting data into mri_output table
set connection_no { }
set insert_normal "insert into mri_output (pwd,ac_my,con_no) values ('$pass','$ac_mth$ac_yr','$sel_con')"
db1 eval insert_normal {} {
}
Table names (and column names) only need to be quoted when they may conflict with keywords in the sql language.
Googling, I found:
Before the SQL-92 standard, it was not legal to have object names (identifiers) in a database that duplicated keywords in the language, were case-sensitive or contained spaces. SQL-92 introduced a single new standard to make any of them legal, provided that the identifiers were defined within pairs of double-quote symbols and were always referred to using double-quote delimiters.
So while sqlite would understand 'mri_output', it is not necessary, and it would be preferred to use double quotes:"mri_output"
John LeSueur
