I'm using pgAdmin 1.6rc1 on Mac OS X 10.4.8 (PowerPC, german
localisation).
- It is somewhat difficult to use the query tool, as entering "n"
will open a new query tool window ("n" is also the shortcut for "new
window")
- Selecting the node trigger functions in the object tree on the left
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,
Belbin, Peter wrote:
a)
I'm using the windows version of the latest 1.6rc1 release of
pgAdmin-III, and have a consistently reproducible error.
Here are the steps to reproduce it:
After selecting a table, and using the context (right-click-popup) menu
and choosing 'View Data->View
