Re: [JDBC] JPA + enum == Exception

From: Vitalii Tymchyshyn <tivv00(at)gmail(dot)com>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tom Dunstan <pgsql(at)tomd(dot)cc>, "Hudson, Derrick" <dhudson(at)redcom(dot)com>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [JDBC] JPA + enum == Exception
Date: 2013-02-09 19:24:57
Message-ID: CABWW-d16=dv++=MbKid6N4iTYGaCxoSr_pWdhRCm3XyVFj13FQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

> This is not entirely unrelated to the discussions about allowing
> broader use of automatic casting server-side. It seems to me that
> on one side of the argument is the idea that strict typing reduces
> bugs and doesn't lead to problems with ambiguity, especially as
> things change; and on the other side the argument is that where no
> ambiguity exists we would make life easier for developers of
> applications or access tools if we relexed things beyond what the
> related specifications require, and that not doing so discourages
> adoption. I think that all the same arguments apply here with
> equal force, on both sides of the issue.
>
> The problem with this debate has always been that both sides are
> completely right. Those are always the toughest to resolve. It
> comes down to which evils we tolerate to garner which benefits. It
> seems that in such cases inertia tends to win. I'm not so sure
> that it should. An ideal solution would find some way to address
> the concerns of both sides, but so far that has eluded us when it
> comes to the type system.
>
>
As for me, "right way" would be to allow exactly same casting as when using
literals. Because now there are a lot of complaints like "It's driver
problem because it works in psql".

Best regards, Vitalii Tymchyshyn

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2013-02-09 20:40:43 Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system
Previous Message Pavel Stehule 2013-02-09 18:30:17 Re: Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used

Browse pgsql-jdbc by date

  From Date Subject
Next Message Guillaume Cottenceau 2013-02-11 08:37:32 Re: RE: [JDBC] é converted in é
Previous Message dmp 2013-02-09 18:36:01 Re: é converted in Ã(c)