[SQL] Standard syntax?

2000-10-12 Thread Franz J Fortuny
I have been using (with success) this SQL statement in PostgreSQL: select col1, case when col2 = true then col3 else col4 end as colw, colM where etc. The above syntax, however, does not work for Interbase (6.01). For those who have had experience in other

[SQL] Referential integrity: broken rule?

2000-10-11 Thread Franz J Fortuny
This table: create table things ( idthing integer not null, isthis boolean not null primary key(idthing,isthis) ) would be referenced by this one: create table forthings ( fromthing integer not null references things(idthing), ) The above SHOULD NOT be accepted, since tabl

[SQL] Re: Speed or configuration

2000-08-23 Thread Franz J Fortuny
00.00..17942.42 rows=34 width=4)EXPLAINWhy Seq Scan if indexes have been created on thecolumns used for access?Best regards,Franz J Fortuny

[SQL] Upper case or lower case....

2000-08-21 Thread Franz J Fortuny
the policy of giving out always upper case names, but I have not been able to find this. It is a hassle to have to transform all the queries which were "select col,col2,col3 from tabname" to "select "COL","COL2","COL3" from "TABNAME" " An unthinkable job. Any suggestions? Franz J Fortuny

[SQL] Speed or configuration

2000-08-21 Thread Franz J Fortuny
17942.42 rows=34 width=4) EXPLAIN Why Seq Scan if indexes have been created on the columns used for access? Best regards, Franz J Fortuny

RE: [SQL] Speed or configuration

2000-08-20 Thread Franz J Fortuny
idle while the other one is active). Memory: 512 MB RAM, 16GB Hard disk. Pentium II (old) I am glad to hear that it's possible to get such good results. I always thought there would be a way. I'll try this query you have suggested... Franz J Fortuny

RE: [SQL] Speed or configuration

2000-08-20 Thread Franz J Fortuny
ws ALWAYS scan table, scan table, scan table. tableY contains about 900,000 rows, and tableX about 65,000. Any more light about the slowness? Franz J Fortuny

[SQL] Speed or configuration

2000-08-20 Thread Franz J Fortuny
certain other queries. But when it comes to the above mentioned query, PostgreSQL simply stays there, forever. The postgres backend must be killed in order to free the client program. Any suggestions? Franz J Fortuny