> Just FYI, I'm adding support for PG's BYTEA column right now. I've
> got it
> working for all object operations (insert/update) and I'm working
> on the
> Manager next. I've implemented it in such a way that bind_param()
> is only
> called if there's at least one column that requires it.
On 7/3/06 8:21 AM, Danial Pearce wrote:
> I've just finished scrolling through your existing discussion started
> here:
>
> http://sourceforge.net/mailarchive/message.php?msg_id=15184811
>
> I also have a bytea column that i'm trying to get data in and out of.
> I've always known in the past that
On 7/3/06 8:21 AM, Danial Pearce wrote:
> I'd be interested to know if you have any plans for proper bytea
> support?
I'm going to explore the possibility of just calling bind_params() once per
"special" field. I'm not sure that's possible, but something I read
recently hinted at it. Failing tha
On 3/22/06 9:43 PM, Sean Davis wrote:
> No error. I just got truncated insertion (presumably from a \000?).
Ah, yeah, it does seem to truncate on null bytes:
my $o1 = Foo->new(b => "\001\000\003");
$o1->save;
my $o2 = Foo->new(id => $o1->id);
$o2->load;
print unpack('H*', $o1->b), "
On 3/22/06 21:31, "John Siracusa" <[EMAIL PROTECTED]> wrote:
> On 3/22/06 8:48 PM, John Siracusa wrote:
>> Looking here:
>>
>> http://www.postgresql.org/docs/8.1/interactive/datatype-binary.html
>>
>> it seems that there's already an ASCII-ified format for bytea columns.
>
> Furthermore, byt
On 3/22/06 8:48 PM, John Siracusa wrote:
> Looking here:
>
> http://www.postgresql.org/docs/8.1/interactive/datatype-binary.html
>
> it seems that there's already an ASCII-ified format for bytea columns.
Furthermore, bytea data seems to round-trip just fine without any fancy DBI
stuff:
# Inse
On 3/22/06 8:38 PM, Daniel Pittman wrote:
> Daniel Pittman <[EMAIL PROTECTED]> writes:
>> Sean Davis <[EMAIL PROTECTED]> writes:
>>> Just tried it and Base64 encoding works fine. I can presumably
>>> inflate and deflate within my RDBO class. Thanks for the idea.
>>
>> Presumably that works becau
Daniel Pittman <[EMAIL PROTECTED]> writes:
[ahem. wrong keystroke, so the rest of my message follows]
> Sean Davis <[EMAIL PROTECTED]> writes:
>> On 3/22/06 2:39 PM, "Sean Davis" <[EMAIL PROTECTED]> wrote:
>>> On 3/22/06 1:36 PM, "John Siracusa" <[EMAIL PROTECTED]> wrote:
On 3/22/06, Sean Da
Sean Davis <[EMAIL PROTECTED]> writes:
> On 3/22/06 2:39 PM, "Sean Davis" <[EMAIL PROTECTED]> wrote:
>> 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 defa
On 3/22/06 6:45 PM, Sean Davis wrote:
> Just tried it and Base64 encoding works fine. I can presumably inflate and
> deflate within my RDBO class. Thanks for the idea.
Yeah, using column triggers...but if you're feeling energetic, you could
also make a proper "blob" column class and associated m
On 3/22/06 2:39 PM, "Sean Davis" <[EMAIL PROTECTED]> wrote:
>
>
>
> 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 s
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.
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 st
13 matches
Mail list logo
