Re: [pgadmin-hackers] Patch: Query favourites
As for the libxml2/msxml - I think going with *just* libxml2 is the way to go. The APIs are so completely different that it would be two completely different implementations. And AFAIK, there are no problems with libxml on Win32 in general. except for libxml2 not being there by default. Neither is wx or libpq, but that doesn't cause a problem. Link with it statically, and the user will never know. So yeah, that can definitly be done without an unreasonable amount of work. If that means that the feature will live, I'm fine with looking at that. But I'd like to know that first. (Implementation details aside of course, there can still be more of those to fix - the feature in principle, and the general idea of storing the data in a file in the users homedir etc) I don't like storing more stuff in files, and in homedir even less. I even don't like registry/.pgadmin3 (not completely replacable), and would like some network (db) based solution to copy server connect strings from. I personally think that's a bad idea. Especially for the config stuff. For favourites, I can see a point in being able to put it centrally - as an option. Then again, storing it in the home directory will make it roam, and that makes it central enough for me. //Magnus ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[pgadmin-hackers] Data type display
Is there a reason why pgAdmin uses internal type names like int2 everywhere, whereas the supposedly user-friendly approach would be that external names like smallint should be used. (Compare to the output of psql and pg_dump.) You can obtain the friendly name using the backend function format_type, which has been available at least since 7.3. This would also avoid the need for manual concatenating with [] for array types. Also, the lists of data types you get when creating a table are not sorted very well. The beginning seems to be alphabetical, but the geometry types are at the end. Perhaps, as an interface improvement, remove all the array types from the list but instead make a separate checkbox Array instead. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [pgadmin-hackers] GrantWizard Property Crack?
Hiroshi Saito wrote: Hi Andreas. I am looking at the strange thing.? see, http://cre-ent.skcapi.co.jp/~saito/pgadmin3/pgAdmin3_GrantWizard_Crack.PNG Do you understand this somehow? Don't have a clue where this comes from: the notebook pages has only the checklistbox and two buttons. Could you use Spy++ to find out the window type/hierarchy? Regards, Andreas ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [pgadmin-hackers] Patch: Query favourites
Dave Page wrote: -Original Message- From: Magnus Hagander [mailto:[EMAIL PROTECTED] Sent: 30 January 2006 20:22 To: Dave Page; Andreas Pflug Cc: pgadmin-hackers@postgresql.org Subject: RE: [pgadmin-hackers] Patch: Query favourites As for the libxml2/msxml - I think going with *just* libxml2 is the way to go. The APIs are so completely different that it would be two completely different implementations. And AFAIK, there are no problems with libxml on Win32 in general. OK, I'll give it a go if I get 5 minutes. So yeah, that can definitly be done without an unreasonable amount of work. If that means that the feature will live, I'm fine with looking at that. But I'd like to know that first. (Implementation details aside of course, there can still be more of those to fix - the feature in principle, and the general idea of storing the data in a file in the users homedir etc) I like the idea, and agree with storing the data in the user's home directory. The data is definitely going to be too large to store sensibly in the registry or an ini file, and storing in the master database restricts you to a single server which, like you, would not help me much. I didn't think of one repository per server, but a dedicated repository server. This would allow roaming regardless of operating systems. Regards, Andresa ---(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
[pgadmin-hackers] SVN Commit by andreas: r4980 - in trunk/pgadmin3: . src/dlg src/schema
Author: andreas Date: 2006-01-31 12:24:02 + (Tue, 31 Jan 2006) New Revision: 4980 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=4980view=rev Log: Fix inherited columns (dont create/edit them) Modified: trunk/pgadmin3/CHANGELOG trunk/pgadmin3/src/dlg/dlgTable.cpp trunk/pgadmin3/src/schema/pgTable.cpp ---(end of broadcast)--- TIP 6: explain analyze is your friend
[pgadmin-hackers] SVN Commit by andreas: r4981 - in branches/REL-1_4_0_PATCHES/pgadmin3/src: dlg schema
Author: andreas Date: 2006-01-31 12:28:45 + (Tue, 31 Jan 2006) New Revision: 4981 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=4981view=rev Log: Fix inherited columns (dont create/edit them) Modified: branches/REL-1_4_0_PATCHES/pgadmin3/src/dlg/dlgTable.cpp branches/REL-1_4_0_PATCHES/pgadmin3/src/schema/pgTable.cpp ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] Patch: Query favourites
-Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 31 January 2006 12:19 To: Dave Page Cc: Magnus Hagander; pgadmin-hackers@postgresql.org Subject: Re: [pgadmin-hackers] Patch: Query favourites I didn't think of one repository per server, but a dedicated repository server. This would allow roaming regardless of operating systems. That's not a bad idea, but it does introduce a whole new level of setup/configuration for the user - perhaps something to consider more fully along with the pgAgent setup. Regards, Dave ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [pgadmin-hackers] Patch: Query favourites
Dave Page wrote: -Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 31 January 2006 12:19 To: Dave Page Cc: Magnus Hagander; pgadmin-hackers@postgresql.org Subject: Re: [pgadmin-hackers] Patch: Query favourites I didn't think of one repository per server, but a dedicated repository server. This would allow roaming regardless of operating systems. That's not a bad idea, but it does introduce a whole new level of setup/configuration for the user - perhaps something to consider more fully along with the pgAgent setup. Hm, don't see the connection to pgAgent. What I was thinking of is an option repository server/db. E.g. when creating a new connection, instead of entering data manually info can be retrieved from repository. Regards, Andreas ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [pgadmin-hackers] Patch: Query favourites
-Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 31 January 2006 16:27 To: Dave Page Cc: Magnus Hagander; pgadmin-hackers@postgresql.org Subject: Re: [pgadmin-hackers] Patch: Query favourites Hm, don't see the connection to pgAgent. What I was thinking of is an option repository server/db. E.g. when creating a new connection, instead of entering data manually info can be retrieved from repository. If we are going to have central repository of some description, then perhaps we should have a wizard to create it for the user. That Wizard could be used to setup the favourites repository, the connection repository, the pgAgent schema and so on, each of which could be setup on one or more servers as required by the user and appropriate for the type of repository (or whatever). Regards, Dave ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] Patch: Query favourites
Dave Page wrote: -Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 31 January 2006 16:27 To: Dave Page Cc: Magnus Hagander; pgadmin-hackers@postgresql.org Subject: Re: [pgadmin-hackers] Patch: Query favourites Hm, don't see the connection to pgAgent. What I was thinking of is an option repository server/db. E.g. when creating a new connection, instead of entering data manually info can be retrieved from repository. If we are going to have central repository of some description, then perhaps we should have a wizard to create it for the user. That Wizard could be used to setup the favourites repository, the connection repository, the pgAgent schema and so on, each of which could be setup on one or more servers as required by the user and appropriate for the type of repository (or whatever). Agred. There's no reason why we can create a Slony cluster from pgAdmin, but not the pgAgent schema (or a future repository schema). Regards, Andreas ---(end of broadcast)--- TIP 6: explain analyze is your friend
[pgadmin-hackers] execute sql script w/o stopping after error?
Does pgadmin3 offer a way to execute sql scripts without stopping if an error is encountered? I've got a script which starts by dropping table (which may or may not exist) and then rebuilds it. If I execute the script with psql (using \i) script execution continues after errors. However if I try to do this with the query tool of pgadmin3 it stops after the drop table statement (if the table doesn't exist). Thanks, Carl B. ---(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-hackers] Query tool: Autocompletion
- select * from pg_cCtrl-Spc) _does_ popup the window. However, the popup will show the same problem as on Windows, remaining on top of all windows. This patch fixes the problem on Windows. Don't have a linux box around to test there, sorry. The patch is simple enough, I think it *should* work... //Magnus autocomplete_popup.patch Description: autocomplete_popup.patch ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[pgadmin-hackers] SVN Commit by dpage: r4983 - in trunk/pgadmin3/src: ctl include/ctl
Author: dpage Date: 2006-01-31 21:42:25 + (Tue, 31 Jan 2006) New Revision: 4983 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=4983view=rev Log: Hide the autocomplete menu if focus is lost [Magnus Hagander] Modified: trunk/pgadmin3/src/ctl/ctlSQLBox.cpp trunk/pgadmin3/src/include/ctl/ctlSQLBox.h ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
