You can think of values in plpgsql as wrapper objects that carry a value and have a "is_null" flag; I have no idea how they're implemented in PostgreSQL or in any RDMBS in general but this should do it, at least for a naive implementation.
Why should i think on simple object MUCH more complicated than it in nature is ?
Let we discuss plpgsql here. Leave the Java to Javers.
I _am_ discussing plpgsql here. And I'm also trying to shed some light on this one.
Now, you think of these things as "MUCH more complicated" because they are NOT simple objects, and if you think that having an integer value that can be NULL is complicated, perhaps you should stick to assembly.
Now, I'm no specialist on this, but it is quite obvious that any data type instance in SQL can have values from:
- its natural domain (arrays of characters, numbers, ip addresses, dates, binary data and so on)
- NULL
Now think of where else you've seen this. It's quite obvious that
"function foo(int)" in plpgsql is like "void foo(Integer i)" or like "void foo(int* i)" and NOT like "void foo(int i)". Now the latter does not put any problems to anyone, does it ? You check that the reference is set and then proceed to use it's value.
Also you might consider giving it a rest and stop shouting in the forum - it's not your back yard you know.
Peace, -- Radu-Adrian Popescu CSA, DBA, Developer Aldrapay MD Aldratech Ltd. +40213212243
---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
