hi all!
thanks for all the feedback on row processing order.
I agree with Greg when he says that the correct way to do this is to set constraints to be deferred.
I think trying to predict a correct row processing order would be really complicated and the problem may not scale given the complexity
Hi all!
consider the following table
table a (id int primary key)
and a particular instance of it:
id
5
6
now update a set id = id +1;
fails if the executor processes row with 5 first.
This means that the query will succeed sometimes and fail at other ti
Hi!
I created a table in postgres with varchar values in it, and I noticed that
postgres lexicographical ordering is weird in the sense that it ignores
whitespaces.
please look at the result I got:
select * from tablename order by columnname;
cloumnname
--
variables (package/schema level) seem like a good feature addition to postgres. If someone could
give us some pointers on how to go about evaluating the feasibility of implementation, that would be very helpful.
thanks
Paramveer Singh
Shridhar Daithankar <[EMAIL PROTECTED]>
15/09/2004 09
that's cool!
one big stumbling block resolved.!
Next I think I would like to look at the remaining exception handling functionality in PL/SQL
One is clearly user defined exceptions.
The PL/SQL documentation says that one must delare user defined exceptions in the DECLARE block
like:
DECLARE
my_exc
Hi!
I am a developer working for a company which typically deploys apps on
Oracle.
We would like to move to postgres for obvious reasons.
However, most of our legacy apps use the exception handling support
provided by PL/SQL.
Instead of porting each of these procedures by hand,
we would like to a
