You are right regarding best practices but I cannot agree with your "do not translate well" Since postgresql officially allows mixed case names for objects, applications have to support it.

Michal

On 20.10.2016 16:34, Melvin Davidson wrote:
*Mark,*
*
*
*Please DO NOT use CamelCase names (or UPPERCASE) in PostgreSQL. By default, PostgreSQL will convert* *all names to lowercase (unless quoted). However, quoting object names is never a good idea and CamelCase* *(or UPPERCASE) names are not necessary. They are a hold over from application programming, but do not
*
*translate well to databases.
*
*
*
Melvin Davidson
I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you.
www.youtube.com/unusedhero/videos
Folk Alley - All Folk - 24 Hours a day
www.folkalley.com



------------------------------------------------------------------------
*From:* Mark Watson <mark.wat...@jurisconcept.ca>
*To:* Melvin Davidson <melvin6...@yahoo.com>; "pgadmin-support@postgresql.org" <pgadmin-support@postgresql.org>
*Sent:* Thursday, October 20, 2016 10:27 AM
*Subject:* RE: [pgadmin-support] pgAdmin4 Maintenance gives Database does not exist

… But if the name of the database contains uppercase characters, the same problem arises :
/psql: FATAL: database ""Dj"" does not exist /
-Mark
*De :*Melvin Davidson [mailto:melvin6...@yahoo.com]
*Envoyé :* Thursday, October 20, 2016 10:09 AM
*À :* Mark Watson; pgadmin-support@postgresql.org
*Objet :* Re: [pgadmin-support] pgAdmin4 Maintenance gives Database does not exist *I am not pgadmin4 support, but this looks to me like the problem is your naming convention.*
*Per PostgreSQL (and SQL) **object names MUST start with a letter**.
<https://www.postgresql.org/docs/9.6/static/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS>*
*https://www.postgresql.org/docs/9.6/static/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS*
*So names a database with a number (even if quoted), is a no no. *
*Try renaming the database to db815, and see if the problem still exists.*
*Melvin Davidson *
    Cell 720-320-0155
*I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you. **Image supprimée par l'expéditeur.**
www.youtube.com/unusedhero/videos
**Folk Alley - All Folk - 24 Hours a day
www.folkalley.com

*
------------------------------------------------------------------------
*From:*Mark Watson <mark.wat...@jurisconcept.ca>
*To:* "pgadmin-support@postgresql.org" <pgadmin-support@postgresql.org>
*Sent:* Thursday, October 20, 2016 8:53 AM
*Subject:* [pgadmin-support] pgAdmin4 Maintenance gives Database does not exist
Hello all,
This is in no way urgent, and concerns pgAdmin4 on windows 10, with postgres 9.6. When I right-click on the database, choose maintence, and run analyze, I am getting a ‘database does not exist’ error. For example, when I try to analyze database 815, I am getting the error : psql: FATAL: database ""815"" does not exist Note the datebase name has two double quotes. Could this be a configuration issue?
Executine analyze in an sql window works fine.
Thanks,
Mark Watson





<<attachment: kozusznik_michal.vcf>>

-- 
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support

Reply via email to