Re: proposal: lob conversion functionality
От | Pavel Stehule |
---|---|
Тема | Re: proposal: lob conversion functionality |
Дата | |
Msg-id | CAFj8pRAygCE4x+cuMLnYhBs70Rmpe5+uYXGT9vC4+fKeG92VHQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: proposal: lob conversion functionality (Noah Misch <noah@leadboat.com>) |
Список | pgsql-hackers |
2013/10/26 Noah Misch <noah@leadboat.com>
On Fri, Oct 25, 2013 at 03:35:05PM +0200, Pavel Stehule wrote:> fixed documentation
> 2013/10/24 Heikki Linnakangas <hlinnakangas@vmware.com>
> > On 22.10.2013 13:55, Pavel Stehule wrote:
> >> 2013/10/21 Noah Misch<noah@leadboat.com>
> >>> If you're prepared to change the function names and add the
> >>> subset-oriented
> >>> functions, I would appreciate that.
> >>>
> >>> here is patch
> >>
> >
> > lobj.sgml still refer to the old names.
Thanks. I made these noteworthy changes:
1. Fix lo_get(oid) on a LO larger than INT_MAX bytes: raise an error rather
than performing a modulo operation on the size.
2. Remove the undocumented ability to pass a negative length to request all
bytes up to the end of the LO. substr() also rejects negative lengths. Note
that one can get the same effect by passing any length >MaxAllocSize.
3. Documentation reshuffling. I placed all the documentation for these
functions in the large objects chapter, and I emphasized the new functions
over the prospect of calling the older functions (whose primary role is to
support client interfaces) from SQL.
If this still looks reasonable, I will commit it.
it is ok
Regards
Pavel
В списке pgsql-hackers по дате отправления: