| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Kris Jurka" <books(at)ejurka(dot)com> |
| Cc: | "Thomas Kellerer" <spam_eater(at)gmx(dot)net>,<pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: bit datatype and getObject() |
| Date: | 2010-12-22 20:32:26 |
| Message-ID: | 4D120BFA02000025000389FA@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Kris Jurka <books(at)ejurka(dot)com> wrote:
> The standard says nothing useful. Section 8.3.3 of this document
> implies that as an application developer you should just pretend
> multi-bit strings don't exist...
BitSet is tempting, but the fuzzy definition of size seems to be a
killer. We clearly don't want to use length() instead of size().
Unless someone can make a convincing argument to the contrary, I'm
inclined to agree that we should just us a Java String of '0' and
'1' characters.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Degrassi Francesco | 2010-12-22 21:09:00 | Re: Postgresql XA prepare() method behaviour |
| Previous Message | Kris Jurka | 2010-12-22 20:13:37 | Re: bit datatype and getObject() |