"Alex Pilosov" <[EMAIL PROTECTED]> writes: > On 15 Nov 2001, Jason E. Stewart wrote: > > > Am I forced to serialize them into strings? Or can I return arbitrary > > SV's from the functions? > Yes, you must serialize. > > The idea is that you use FreezeThaw or Storable method to serialize your > incoming data before passing it along to database. Your data can be as > complicated as you want (hashes of arrays of hashes, etc). On database > side, you deserialize them and process. Then again, you serialize the > return value[s] and decode them on client side.
Grrrr.... I'm sure that Storable is fast at what it does, but I don't see why the data must be serialized in the first place. If Pg can pass char*'s back and forth, why shouldn't it be able to pass void*'s? That way I could pass an SV* to an arbitrary data structure. I've got tables that will have millions of rows, and I don't want to have to serialize them at all, that's just wasted computation. > > What about using bind_param_inout()? The DBD::Pg man page says > > this isn't supported, but would implementing this enable me to > > pass back RV's? > > PostgreSQL doesn't support out/inout parameters... Ok. Is this because there aren't enough warm bodies to actually write the code, or because there is some fundamental issue that prevents it from happening? Even so. If it did exist, would it enable me to pass void*'s to and from the stored procedures? Thanks, jas.
