Re: [pgadmin-support] bug in 1.6 rc1
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 All Rows' to get the Edit Data window, then selecting row and column defined as 'character varying(65000)', and editing the contained xml, moving away (clicking on another row) produces the following error message: Can you enable query logging on your server and see what is actually being sent to the server please? Subsequent attempts to move to another row produces a dialog box querying whether I want to save changes, which leads to another of the above messages appearing. Ie: it enters some sort of loop where it knows data has not been saved, but errors out when trying to save it, which sets it up for another iteration of the error cycle. That's intended - it's so you don't lose the text you might have just spend five minutes typing in (which can be annoying if the error was caused by a simple constraint error for example. To get out of the loop, after you see the error either fix it, or hit the undo button to revert the changes you've made. I rather like the ability to just bring up the entire table with a single click rather than continually having to navigate into the sub-menu of the context menu that appears when you're on a table / view type object in the hierarchy on the left. Is there a way to customize the context menu so that the 'favourite' edit window option can be moved to the top layer of the context menu to save having to continually navigate into the sub-menu? This would be a nice customization capability if it's not already there. if it is already there, do tell. No, this is not currently possible on the context menu, but you can just hit the button on the toolbar. Regards, Dave ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[pgadmin-support] Does pgAdmin have to double-quote table and field names?
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, btw, thanks to all of the contributors. -- View this message in context: http://www.nabble.com/Does-pgAdmin-have-to-double-quote-table-and-field-names--tf2574512.html#a7177095 Sent from the PostgreSQL - pgadmin support mailing list archive at Nabble.com. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-support] Does pgAdmin have to double-quote table and
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). pgAdmin automatically quotes identifiers if you use a name that requires them. > 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? No, you cannot turn it off, and yes, it is safe as long as you remember to quote things appropriately outside of pgAdmin. See http://www.postgresql.org/docs/8.1/static/sql-syntax.html#SQL-SYNTAX-IDENTIFIERS for more info. It's a very nice package, btw, thanks to all of the contributors. You're welcome. Regards, Dave ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [pgadmin-support] Does pgAdmin have to double-quote table and
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 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). pgAdmin automatically > quotes identifiers if you use a name that requires them. > > > 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? > > No, you cannot turn it off, and yes, it is safe as long as you remember > to quote things appropriately outside of pgAdmin. See > http://www.postgresql.org/docs/8.1/static/sql-syntax.html#SQL-SYNTAX-IDENTIFIERS > > for more info. > >> It's a very nice package, btw, thanks to all of the contributors. > > You're welcome. > > Regards, Dave > > ---(end of broadcast)--- > TIP 6: explain analyze is your friend > > -- View this message in context: http://www.nabble.com/Does-pgAdmin-have-to-double-quote-table-and-field-names--tf2574512.html#a7177919 Sent from the PostgreSQL - pgadmin support mailing list archive at Nabble.com. ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
[pgadmin-support] GUI glitches in 1.6rc1 for Mac OS X
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
doesn't show the list in the panel on the right (as all other entries
do)
- The About Menu contains "Auffrischen F5" with the main window
topped and it DOES a refresh. With the query window on top, the menu
entry text is ok (About...) but nothing happens after selecting it
Regards
Helmut
---(end of broadcast)---
TIP 6: explain analyze is your friend
