Re: Postgres 8.3 broke everything

Yeah - I pressed tab to indent my code, and of course it tabbed to the
next element on the page, which was the send button, then I hit a key,
and it sent the message before I was ready. I tested my hypothesis,
but it was wrong. I haven't quite figured it out yet. Something to
do with casting a char to an int I think, but I can't reproduce it
yet. I think it might only be in prepared statements, all I know is
that somewhere the behaviour changed, but I don't know yet that it's
definitely Postgresql that changed, but it all started when I
upgraded. It's my own stupid fault for the way I'm using JSTL, it's
what I get for doing ${param.keyId} in a <sql:param> hoping that it
would just cast it like it does in a bean. Sometimes it worked, and
other times it didn't, except that mostly it did.

Alex

On Thu, Feb 21, 2008 at 6:07 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> On Thu, 21 Feb 2008 17:53:35 -0500
> "Alex Turner" <armtuk(at)gmail(dot)com> wrote:
>
> > Upgrading to Postgres 8.3 broke virtually every site we host, and I
> > finally figured out why. In 8.2 you could do this:
> >
> > create table foo (
>
> No that would fail.
>
> Did you forget the rest of your message? :)
>
> Joshua D. Drake
>
>
> - --
> The PostgreSQL Company since 1997: http://www.commandprompt.com/
> PostgreSQL Community Conference: http://www.postgresqlconference.org/
> Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
> PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFHvgQUATb/zqfZUUQRAsULAJ9KE29XS7jx2M88b62/wSM252jvWACdERA4
> RBy/uiLQHgsd9/t56C0wUz8=
> =Ad7K
> -----END PGP SIGNATURE-----
>