Re: BLOB support

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BLOB support
Дата
Msg-id 26289.1307369606@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: BLOB support  (Radosław Smogura <rsmogura@softperience.eu>)
Ответы Re: BLOB support  (Radosław Smogura <rsmogura@softperience.eu>)
Re: BLOB support  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Список pgsql-hackers
Radosław Smogura <rsmogura@softperience.eu> writes:
>  I think more about this with contrast to sent references, but I still 
>  have in my mind construct
>  Blob myWeddingDvd = conn.createBlob(myWeddingStream, size); //A bit 
>  outdated we have BlueRay
>  conn.prepareStatemnt("INSERT INTO someonetubevideos values (?)")
>  where 1st parameter is myWeddingDvd,

Yes, if you insist upon designing the API like that, then you come to
the conclusion that you need global LOB identifiers.

However, there are many ways to design this that don't work that way.
One idea to think about is
insert into someonetubevideos values('')returning open_for_write(videocolumn)

which gives you back some kind of writable stream ID (this is a
transient, within-session ID, not global) for the target field in the
row you just inserted.

BTW, as was noted upthread by Dimitri, this whole subject has been
discussed before on pgsql-hackers.  You really ought to go re-read the
previous threads.
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: WIP: AuthenticationMD5 protocol documentation clarification
Следующее
От: Simon Riggs
Дата:
Сообщение: Re: reducing the overhead of frequent table locks - now, with WIP patch