[SQL] Making dirty reads possible?

Hi co-fanatics. I am working on a small prove of concept, and am running into a small obstacle. (the prove of concept showing, amongs other things, that doing calculations on a database works well, and that it is possible to let it run 'jobs') Considder the following stored procedure: For rea

[SQL] Set Returning Function problem

Hi, I noticed what i think is a weird behaviour with SRFs. When I use them in a SELECT clause, and the SRF returns no rows, the query returns no rows too, when I think it should return an a null column. I'm posting an example below: test=> CREATE TABLE foo (cod SERIAL, bar TEXT); NOTICE: CREAT

Re: [SQL] Set Returning Function problem

Alvaro Nunes Melo <[EMAIL PROTECTED]> writes: > I noticed what i think is a weird behaviour with SRFs. When I use them > in a SELECT clause, and the SRF returns no rows, the query returns no > rows too, when I think it should return an a null column. Why would you think that? The behavior is exac

Re: [SQL] Making dirty reads possible?

[EMAIL PROTECTED] writes: > But not possible for real at the moment? > > So, summarising: > - Nested transactions is not (yet) supported > - READ UNCOMMITTED isolation level is not (yet) supported > - the EXECUTE plpgsql construct does not circumvent the transaction Well nested transactions are

Re: [SQL] Making dirty reads possible?

Guys, > I find I've been stymied using server-side functions for large batch jobs > for pretty much the same reason. I find it works better and it's more > flexible to write client-side programs in the language of my choice that > connect to the database and do the batch jobs. FWIW, Gavin Sherry

[SQL] Making dirty reads possible?

Hi co-fanatics. I am working on a small prove of concept, and am running into a small obstacle. (the prove of concept showing, amongs other things, that doing calculations on a database works well, and that it is possible to let it run 'jobs') Considder the following stored procedure: For re

[SQL] MO: SQL Query Performance tips

Hi All, I have a partial table structure as below tbl_user_main user_id pk user_level references tbl_level user_class references tbl_class user_level references tbl_level tbl_level level_id pk level_name level_points tbl_weapon wea

[SQL] Postgesql 8 beta 5: ecpg and date type - Access violations

Hi,   There is an "access violation" caused by ecpgtypes when using date fields and ecpg. Everything was runnig ok with dates rangin from 2000 - 2004, but this acces violation occurs when the date with th year 1968 appears.   Looking at my program, I can see that this happens inside the SELE