> I am not sure what your exact purpose is, but in doing a lot of web
> work with pgsql, I usually just store the full path to the image in a
> varchar field and fetch that right into the IMG SRC attribute when I
> need to display the image.
Why would a full path in a IMG tag work? Doesn't your
On Sun, Mar 11, 2001 at 08:48:21PM -0500, Tom Lane wrote:
[ . . . ]
> bytea is probably your best bet. The 8k limit is toast in 7.1, btw.
Is that whay you named it TOAST, in order to be able to say that? :)))
Regards, Frank
---(end of broadcast)-
> bytea is probably your best bet. The 8k limit is toast in 7.1, btw.
If you're using JDBC, you may not be able to get bytea types to work. I was
able to get the SQL type OID to work with JDBC's get/setBytes() methods.
You may also want to use 7.1 since I believe it's large object support is
im
<[EMAIL PROTECTED]> writes:
> I would like to store some images in my Postgres database. These will
> all be thumbnails, limited to 4k or 5k. I know that PG has an 8k row
> limit, but this should be fine, because there's not much else in the
> row. Which data type could I use to store them, and
I would like to store some images in my Postgres database. These will
all be thumbnails, limited to 4k or 5k. I know that PG has an 8k row
limit, but this should be fine, because there's not much else in the
row. Which data type could I use to store them, and is there a
performance cost for ha
