Forum OpenACS Development: Response to Porting update procedures from oracle to pg

Collapse
Posted by Tom Jackson on

I guess I should look at the hacked db_exec_plsql, but I guess there are certain things I don't understand here. In Oracle/ACS, you can call a function with named parameters, but not in postgresql. So if I have a pg functions with 10 parameters, do I have to have 10 parameters for every call to this function? I'm sure that I do. If that is right, then porting calls inside db_exec_plsql will have to be expanded to include all parameters.

Another issue is NULLs. Isn't pg supposed to handle NULLs more explicitly than Oracle. NULL != ''? Can I use a NULL parameter value as a key to update as I did in the set_attrs procedure above?