Keith C. Perry wrote:
I would think you really can't or **probably** would not
manipulate byteas in pgadmin. Could there not be and option to "ignore" a bytea
field(s) (i.e. a placeholder or some sort) so that you can insert, update, etc
other record fields without having to wait for bytea fie
Keith C. Perry wrote:
Great. I'll work around it for now but dare I ask... do you have a timetable
for the beta releases? I think I know the answer but you know I had to ask :)
We're heading for *release* in-time with PostgreSQL 8.1, due end of this
month or so.
Regards,
Andreas
-
Great. I'll work around it for now but dare I ask... do you have a timetable
for the beta releases? I think I know the answer but you know I had to ask :)
Quoting Andreas Pflug <[EMAIL PROTECTED]>:
> Keith C. Perry wrote:
>
>
> >
> > I would think you really can't or **probably** would not
Keith C. Perry wrote:
I would think you really can't or **probably** would not manipulate
byteas in pgadmin. Could there not be and option to "ignore" a bytea
field(s) (i.e. a placeholder or some sort) so that you can insert,
update, etc other record fields without having to wait for bytea
I'm not sure if this is something that has been discussed before. I did a
archive search and didn't find anything...
The problem I'm having is that I have a table with a bytea field that is used to
store a file- not necessary large files, they could be but I saw this behavior
with something where
