Re: Review: Patch: Allow substring/replace() to get/set bit values

Started by Kevin Grittnerabout 16 years ago3 messageshackers
Jump to latest
#1Kevin Grittner
Kevin.Grittner@wicourts.gov

Leonardo F wrote:

New version of the patch, let me know if I can fix/change something
else.

All issues addressed, with one tiny nit-pick -- the get_bit and
set_bit methods are not part of the SQL standard. I took the liberty
of removing "SQL-standard" from the documentation of these functions
so that I can mark this "Ready for Committer".

Thanks for the patch!

-Kevin

Attachments:

getsetbit.patchapplication/octet-stream; name=getsetbit.patchDownload+238-10
#2Leonardo Francalanci
m_lists@yahoo.it
In reply to: Kevin Grittner (#1)
Re: Review: Patch: Allow substring/replace() to get/set bit values

All issues addressed, with one tiny nit-pick -- the get_bit and
set_bit methods are not part of the SQL standard.

Damn! I completely forgot to mention that I had no idea if what I wrote
in the docs made any sense...

Well thank you for your thorough review.

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Kevin Grittner (#1)
Re: Review: Patch: Allow substring/replace() to get/set bit values

"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:

Leonardo F wrote:

New version of the patch, let me know if I can fix/change something
else.

All issues addressed, with one tiny nit-pick -- the get_bit and
set_bit methods are not part of the SQL standard. I took the liberty
of removing "SQL-standard" from the documentation of these functions
so that I can mark this "Ready for Committer".

Applied with some further editorialization. When I looked at how
OVERLAY(text) was implemented, I didn't like it at all, so I took the
liberty of transforming it to C code and then duplicating that
implementation for bit and bytea. I doubt this would make any
performance difference in simple cases, but it will have less surprise
factor.

regards, tom lane