novnov wrote:
Is there anything like SOP for pgsql devs then? Do most stick to lowercase
everywhere, and skip the issues, or do they keep the namestyles like
"ItemName" and just accomodate the need to double quote when it arises? I am
sure good devs could go either way, but curious if you or othe
Thanks again.
Is there anything like SOP for pgsql devs then? Do most stick to lowercase
everywhere, and skip the issues, or do they keep the namestyles like
"ItemName" and just accomodate the need to double quote when it arises? I am
sure good devs could go either way, but curious if you or othe
novnov wrote:
Hi Dave and thanks for responding.
I have to worry about the SQL syntax because practically the first thing I
did after using pgAdmin to create the tables was to try to write a stored
proceedure with pgAdmin against the table. The stored proceedure wouldn't
work until I manually ad
Hi Dave and thanks for responding.
I have to worry about the SQL syntax because practically the first thing I
did after using pgAdmin to create the tables was to try to write a stored
proceedure with pgAdmin against the table. The stored proceedure wouldn't
work until I manually added the double
novnov wrote:
I am having a discussion re pgsql double quoting or not in the General
mailing list, it's buried in the thread titled "Simple stored procedure
examples?" As far as I understand things, pgsql ignores case, unless I
explicitly use surround table and field names etc with double quotes.
I am having a discussion re pgsql double quoting or not in the General
mailing list, it's buried in the thread titled "Simple stored procedure
examples?" As far as I understand things, pgsql ignores case, unless I
explicitly use surround table and field names etc with double quotes. If I
use the d
I see, so to make it explicit, if I'd named my table item not Item, and the
column itemname not ItemName, pgAdmin (and pgsql) wouldn't need to double
quote. Not my preference but I'll live.
Thanks
Dave Page-3 wrote:
>
> novnov wrote:
>> As far as I can tell pgsql itself does not require table
novnov wrote:
As far as I can tell pgsql itself does not require table and field names to
be wrapped in double quotes, but pgAdmin does that by default (at least on
windows).
PostgreSQL does require you to use double quotes in some circumstances
(for example, if you use upper case letters). p
As far as I can tell pgsql itself does not require table and field names to
be wrapped in double quotes, but pgAdmin does that by default (at least on
windows). What's the rationale? I've not found a way to turn this off in
pgAdmin, is there a way, is it safe to do this?
It's a very nice package,
