On 3/22/06 1:36 PM, "John Siracusa" <[EMAIL PROTECTED]> wrote:
> On 3/22/06, Sean Davis <[EMAIL PROTECTED]> wrote:
>> Why is the type for "contents" a scalar?
>
> Because that's the default when there is not a more specific RDBO
> column type mapped to whatever DBI returns for the column type.
>
>> I would like to store binary data in that column, which I can do with
>> straight
>> DBI, but it seems I have to specify the bind_type as DBD::Pg::PG_BYTEA.
>
> Is there no other way to use a bytea column using DBI? For example,
> will it accept a base64 encoded string or something? If not, then
> RDBO will have to be changed to add support for explicit bind types
> for individual column values.
>
> Right now, RDBO binds by passing arguments to DBI's execute() method.
> To add explicit binding of each column, RDBO would have to loop and
> call bind_param() individually on each column value. There's a
> performance hit associated with doing that, so I've been avoiding it
> thus far. But if there's really no other way to handle Pg bytea
> columns, then I guess I'll have to add it.
Thanks again, John. Let me check around a bit. I'm way too new to storing
binary data (and DBD::Pg may be changing here, from the looks of
it--SQL_BINARY is being deprecated in favor of PG_BYTEA, according to the
1.47 docs) to know what is the "best" way to do it.
Sean
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object
