[pgadmin-support] problem adding a foreign key in v1.5 and a question re v1.5 vs 1.2.2
hi! i'm using pgadmin3 v1.5 devel, built today from a fresh cvs checkout. with this version i am having problems adding foreign keys (to existing tables or when creating a new table) since pgadmin doesn't seem to refresh the columns in the selected table and i cannot select a column to specify it as a referencing column. the pull-down list contains the name of the first column from the table which was selected by default when the dialog window opened. i wanted to try it with v1.2.2 but that version no longer recognizes any information about the servers. it realizes that i have 2 servers on the list but instead of the server names the string "(:0)" is written and in the server properties all values are blank. i find this a bit strange because i recall having no problems using either version of pgadmin a short while ago. i am running pgadmin3 on suse linux 9.3. please tell me if you need me to provide additional information and / or images. regards, Miha ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [pgadmin-support] problem adding a foreign key in v1.5 and a
Miha Radej wrote: hi! i'm using pgadmin3 v1.5 devel, built today from a fresh cvs checkout. with this version i am having problems adding foreign keys (to existing tables or when creating a new table) since pgadmin doesn't seem to refresh the columns in the selected table and i cannot select a column to specify it as a referencing column. Please specify the situation when you miss the columns. the pull-down list contains the name of the first column from the table which was selected by default when the dialog window opened. i wanted to try it with v1.2.2 but that version no longer recognizes any information about the servers. it realizes that i have 2 servers on the list but instead of the server names the string "(:0)" is written and in the server properties all values are blank. i find this a bit strange because i recall having no problems using either version of pgadmin a short while ago. The registry format changed a day ago; the old was getting too crowded. 1.5 will convert from older versions. Regards, Andresa ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgadmin-support] problem adding a foreign key in v1.5 and a
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Andreas Pflug > Sent: 11 November 2005 15:53 > To: Miha Radej > Cc: 'pgadmin-support@postgresql.org' > Subject: Re: [pgadmin-support] problem adding a foreign key > in v1.5 and a > > The registry format changed a day ago; the old was getting > too crowded. > 1.5 will convert from older versions. Oh, is that what deleted all my servers? Took me ages to put them back again :-( /D ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [pgadmin-support] problem adding a foreign key in v1.5 and a question re v1.5 vs
hi! the foreign key problem seems to come from using an incorrect schema name. ie. in a database i am using i have a few schemas. i am working on one of them and when selecting a referencing table all table names are displayed as 'schema.tablename' except the tables from the current schema i'm working on, where just the form 'tablename' is used. and pgadmin3 appears to use the public schema if no schema seems to be specified, which then returns no columns. ie: i am working on a schema called 'myschema' and i select a table 'tablename' as a referenced table. pgadmin generates the following query to retrieve the column names from a newly selected table: SELECT attname FROM pg_attribute att, pg_class cl, pg_namespace nsp WHERE attrelid=cl.oid AND relnamespace=nsp.oid AND nspname='public' AND relname='tablename' AND attnum > 0 ORDER BY attnum instead of SELECT attname FROM pg_attribute att, pg_class cl, pg_namespace nsp WHERE attrelid=cl.oid AND relnamespace=nsp.oid AND nspname='myschema' AND relname='tablename' AND attnum > 0 ORDER BY attnum regards, Miha ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [pgadmin-support] problem adding a foreign key in v1.5 and a
Dave Page wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andreas Pflug Sent: 11 November 2005 15:53 To: Miha Radej Cc: 'pgadmin-support@postgresql.org' Subject: Re: [pgadmin-support] problem adding a foreign key in v1.5 and a The registry format changed a day ago; the old was getting too crowded. 1.5 will convert from older versions. Oh, is that what deleted all my servers? Took me ages to put them back again :-( Um yes, old registry entries are deleted after creation in the new location to avoid that new entries are overwritten by old ones. Regards, Andreas ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgadmin-support] problem adding a foreign key in v1.5 and a
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 11 November 2005 16:14 > To: Dave Page > Cc: Miha Radej; pgadmin-support@postgresql.org > Subject: Re: [pgadmin-support] problem adding a foreign key > in v1.5 and a > > Dave Page wrote: > > > > > > > >>-Original Message- > >>From: [EMAIL PROTECTED] > >>[mailto:[EMAIL PROTECTED] On Behalf Of > >>Andreas Pflug > >>Sent: 11 November 2005 15:53 > >>To: Miha Radej > >>Cc: 'pgadmin-support@postgresql.org' > >>Subject: Re: [pgadmin-support] problem adding a foreign key > >>in v1.5 and a > >> > >>The registry format changed a day ago; the old was getting > >>too crowded. > >>1.5 will convert from older versions. > > > > > > Oh, is that what deleted all my servers? Took me ages to > put them back > > again :-( > > Um yes, old registry entries are deleted after creation in the new > location to avoid that new entries are overwritten by old ones. Whatever killed mine off didn't delete them, it just set all the settings to empty strings so I had lots of servers like: (:0) as Miha did :-( What's also odd, is that looking in the registry, I still seem to be using the old format having re-added my servers. Obviously I haven't picked up the change yet, which makes me wonder what blew all the entries away. /D PS. Just rebuilt - settings upgraded fine. Now how do I test fixes in 1.4.x without getting in a mess I wonder... /D ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[pgadmin-support] Feature requests
To whom it may concern, First of all I would like to thank all who worked on the new pgAdmin: the new style and graphical explains are super! Nevertheless I ran into a "bug", or maybe better: a feature-request. When one is creating a new foreign key via the tool, it is not possible to select "no action" for either "on update" or "on delete". This is a pitty, because "restrict", which is almost the same, doesn't allow constraints to be deferrable. In order to solve this, the constraints have to be made via the query tool. Another request would be to able to "change" foreign key properties (like Deferrable, Deferred, On Update, etc..). When applying the changes pgAdmin would than drop the foreign key and recreate it with the new settings. To garanty consistency the table could be locked exclusively. A final request would be to have "mouseover hints". This would really benefit new user (and experienced ones with new features)! Hopefully these suggestions are usefull to you and can we benefit from them in the (near) future. Your sincerely, Aarjan Langereis
Re: [pgadmin-support] [pgadmin-hackers] pgAdmin v1.4.0 Released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Packages for Debian/sarge have just been uploaded to our master host. PostgreSQL mirrors should sync in the next hours. Regards, Raphaël for the pgAdmin Development Team Dave Page wrote: > I'm pleased to announce the release of pgAdmin 1.4.0, the Open Source > graphical PostgreSQL administration tool for Windows, Linux, FreeBSD, > Mac OS X and Solaris, now available for download in source and a > variety of binary formats from: > > http://www.postgresql.org/ftp/pgadmin3/release/v1.4.0/ > > V1.4.0 contains a number of new features over previous releases, > including: > > - Slony-I support > - An SQL/shell job scheduling agent > - PostgreSQL 8.1 support > - Autovacuum administration > - Roles > - Stored procedures (ie. Functions with OUT parameters) > - Prepared transactions > - Allow server registration without connect > - Allow connection selection in the query tool > - Major source tree and architecture overhaul to allow further > extensibility > - Unix domain socket support > - 'Guru Hints' to help new users > - Password can be stored in .pgass/pgpass.conf files > - New graphics throughout > - Alert the user when a query finishes in the query tool if the window > is > not active > - Graphical EXPLAIN > - Support for Asynchronous Notifications in the query tool > > As well as many other tweaks, improvements and bug fixes, details of > which > may be found on the changelog at: > > http://www.pgadmin.org/development.php#changelog > > For more information about pgAdmin, please visit the website at: > > http://www.pgadmin.org/ > > I would like to take this opportunity to thank all those who gave their > time to help with the development, testing, translation and packaging of > this release. > > Dave Page > pgadmin Development Team > > ---(end of broadcast)--- > TIP 2: Don't 'kill -9' the postmaster > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDdSIKx3NpDPptARMRArBOAKCoZvH/VOqK1q+yWPgf36m35kGXlgCfSOzJ 1fWM3Sm2BeRBY/lqibxJ5M0= =GYMg -END PGP SIGNATURE- ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
