Re: BLOB issue(s) & questions
От | Dave Page |
---|---|
Тема | Re: BLOB issue(s) & questions |
Дата | |
Msg-id | 03AF4E498C591348A42FC93DEA9661B889F26A@mail.vale-housing.co.uk обсуждение исходный текст |
Ответ на | BLOB issue(s) & questions (Derek Shaw <derek@bisi.ca>) |
Ответы |
Re: BLOB issue(s) & questions
|
Список | pgsql-odbc |
> -----Original Message----- > From: Derek Shaw [mailto:derek@bisi.ca] > Sent: 09 February 2004 20:30 > To: pgsql-odbc > Subject: [ODBC] BLOB issue(s) & questions > > Can anyone shed any light on how serious this problem is, > what the problem actually might be, and whether it is ever > likely to be resolved so that I could use PostgreSQL? Hi Derek, There are three options: 1) Use a bytea column. You might create a domain as an 'lo' alias to bytea if required. 2) Use the /contrib/lo code. This custom datatype allows you to create a cleanup trigger for each lo column. 3) Use the 'simple' ODBC lo option documented at: http://gborg.postgresql.org/project/psqlodbc/faq/faq.php?faq_id=52 - this does not cleanup after itself, however in /contrib/vacuumlo is a small utility that will remove orphaned large objects - just run it prior to a normal vacuum, or at whatever frequency suits if you use the autovacuum daemon. Please note that I haven't tried using blobs in years... Regards, Dave.
В списке pgsql-odbc по дате отправления: