On 08/05/2016 10:41, Klaus P. Pieper wrote:
> For me is the way Sybase works is just more convenient:
>
> CREATE MyTable (MyColumn varchar);
>
> creates a camel cased table MyType and field MyColumn.
>
> SELECT * FROM SYSCATALOG gives MyTable.
>
> This is better readable when you use long t
> -Ursprüngliche Nachricht-
>
> What exactly is the problem you are trying to solve?
>
> If you and your users are consistent about never using quotes, your users
can
> write:
>
> SELECT MyColumn FROM MyTable ORDER BY MyColumn;
>
> It will select mycolumn from mytable, but that doesn't
On 2016-04-29 19:21:30 +0200, Evgeny Morozov wrote:
> It would be great if Postgres had a server setting that allowed the automatic
> folding of identifiers to lowercase to be disabled, so that camel case
> identifiers could be used without having to quote every single identifier,
> i.e.
>
> SELE
Le 3 mai 2016 7:01 PM, "Evgeny Morozov"
a écrit :
>
> That's an interesting idea! The client users would use is probably
pgAdmin. I don't know whether pgAdmin parses the query, though. If it does
then it should be relatively easy to add this. If not, I'd imagine it's not
going to happen.
>
The pg
That's an interesting idea! The client users would use is probably pgAdmin.
I don't know whether pgAdmin parses the query, though. If it does then it
should be relatively easy to add this. If not, I'd imagine it's not going
to happen.
On 2 May 2016 at 13:59, John McKown wrote:
> On Mon, May 2, 2
On Mon, May 2, 2016 at 3:03 AM, Evgeny Morozov <
evgeny.morozov+list+pg...@shift-technology.com> wrote:
> On 30 April 2016 at 01:31, Tom Lane wrote:
>
>> Yeah, this isn't going to happen. Years ago we looked into what it would
>> take to be able to flip a switch and have the standard-compliant b
On 30 April 2016 at 01:31, Tom Lane wrote:
> Yeah, this isn't going to happen. Years ago we looked into what it would
> take to be able to flip a switch and have the standard-compliant behavior
> (fold to upper not lower). It was impractical then and no doubt is far
> more so now. I do not rem
John McKown writes:
> âOh well, it's been interesting, but I don't think that we'll come to a
> resolution for the OP on this issue. I just blame both PostgreSQL and MySQL
> for this problem because the SQL standard says that the names are
> automatically UPPERCASEd unless enclosed in quotes. No
On Fri, Apr 29, 2016 at 3:38 PM, John R Pierce wrote:
> On 4/29/2016 12:56 PM, John McKown wrote:
>
> I suspect this would be painful for the parser, unless you also enforced
>> that all SQL keywords were in a specific case (all lower would be the
>> minimal impact to the code). otherwise the p
On Fri, Apr 29, 2016 at 3:38 PM, John R Pierce wrote:
> On 4/29/2016 12:56 PM, John McKown wrote:
>
> I suspect this would be painful for the parser, unless you also enforced
>> that all SQL keywords were in a specific case (all lower would be the
>> minimal impact to the code). otherwise the p
On 4/29/2016 12:56 PM, John McKown wrote:
I suspect this would be painful for the parser, unless you also
enforced that all SQL keywords were in a specific case (all lower
would be the minimal impact to the code). otherwise the parser
would have to lower() every token to check to
On Fri, Apr 29, 2016 at 2:44 PM, John R Pierce wrote:
> On 4/29/2016 10:21 AM, Evgeny Morozov wrote:
>
> It would be great if Postgres had a server setting that allowed the
> automatic folding of identifiers to lowercase to be disabled, so that camel
> case identifiers could be used without havin
On 4/29/2016 10:21 AM, Evgeny Morozov wrote:
It would be great if Postgres had a server setting that allowed the
automatic folding of identifiers to lowercase to be disabled, so that
camel case identifiers could be used without having to quote every
single identifier, i.e.
SELECT MyColumn FRO
It would be great if Postgres had a server setting that allowed the
automatic folding of identifiers to lowercase to be disabled, so that camel
case identifiers could be used without having to quote every single
identifier, i.e.
SELECT MyColumn FROM MyTable ORDER BY MyColumn
instead of
SELECT "M
14 matches
Mail list logo
