Re: [pgadmin-hackers] Work on pgAdmin3
Dave Page wrote: OK, that's an ambitious statement. I'll look forward to seeing the results. I'll send you something as soon as it works Still as I said, I'm not prepared to give out CVS write access upon request - I doubt very much you will find any serious project that does. Sure. I would also suggest that you do keep the list up to date on any work you are doing. There are other people working on their own copies of the code, and it is possible that I will find time to do so again once the new financial year starts. The last thing any of us would want is duplication of effort. If someone's doing something right now, we probably will do duplicates, as I implement the whole tree with slight redesigns (no tvXXX or svXXX, virtual functions instead to keep frmMain/browser.cpp smaller). In your new design, have you considered the cacheing issues that Keith I discussed recently? I'm tracking this list since Jan 24, haven't seen something about cacheing. Did I miss it? Regards, Andreas ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [pgadmin-hackers] todo question?
-Original Message- From: Jean-Michel POURE [mailto:[EMAIL PROTECTED] Sent: 27 March 2003 09:08 To: pgadmin-hackers Subject: Re: [pgadmin-hackers] todo question? Le Mercredi 26 Mars 2003 23:12, Dave Page a écrit : I think the idea here was to create something similar to Oracle packages(?). Jean-Michel, do you remember the details - I think that was you one wasn't it? This was before schema was introduced. The idea was to be able to group objects and export them to SQL. The concept is obsolete. Now the schema exist. It is not more from making? Bye !! Frank Lupo (Wolf) !! /\_ _/\ \ o o / --ooo-ooo--- -- Prendi GRATIS l'email universale che... risparmia: http://www.email.it/f Sponsor: Tutti i nuovi modelli di telefonia su Ebest Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=550d=27-3 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
[pgadmin-hackers] WARNING: CVS Server potential downtime
Hi all, I won't go into the long and complex story, but due to a mistake by the ISP who provide the connection to the pgAdmin CVS server, there are likely to connection issues over the next week or so whilst the leased line is changed twice(!). Apologies for any inconvenience this may cause... Regards, Dave. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [pgadmin-hackers] Work on pgAdmin3
-Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 27 March 2003 11:36 To: Dave Page; [EMAIL PROTECTED] Subject: Re: [pgadmin-hackers] Work on pgAdmin3 I'm tracking this list since Jan 24, haven't seen something about cacheing. Did I miss it? It was in amongst a bunch of other subjects in one email thread between me Keith. Basically, in pgAdmin II, pgschema provides a single object hierarchy that can be used by all parts of pgadmin. This meant that as the hierarchy was built on demand, it happened for any part of the application that accessed it. The difficult bit was synchronising the pgschema hierarchy with the treeview. In pgAdmin III, that problem doesn't exist because the object hierarchy is maintained by the treeview which stores each object as a class derived from wxTreeItemData (iirc). However, this method relies on the user to click the treeview to build the hierarchy, so something like Keith's QBE tool cannot use the hierarchy to find available tables/views etc because they may not be there if the user hasn't browsed to them. This of course also applies to other dialogues that may provide lists of objects, such as create operator, create function etc etc. I have yet to figure out a solution (other than return to the old style design), and I'm guessing Keith hasn't either as he hasn't said so. Regards, Dave. ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-hackers] Work on pgAdmin3
Hi Dave, what I'm doing now can't be possibly called a patch... You won't hear from me in this list until pgAdmin3 can browse and execute as pgAdmin2 does I'll be back soon. Regards, Andreas Dave Page wrote: Excellent. Any contributions would be gratefully received... I'm happy to grant CVS write access, but as I'm sure you understand, I'll need to see at least a couple of good quality patches of reasonable size submitted before doing so. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] Work on pgAdmin3
-Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 27 March 2003 11:10 To: Dave Page; [EMAIL PROTECTED] Subject: Re: [pgadmin-hackers] Work on pgAdmin3 Hi Dave, what I'm doing now can't be possibly called a patch... You won't hear from me in this list until pgAdmin3 can browse and execute as pgAdmin2 does OK, that's an ambitious statement. I'll look forward to seeing the results. Still as I said, I'm not prepared to give out CVS write access upon request - I doubt very much you will find any serious project that does. I would also suggest that you do keep the list up to date on any work you are doing. There are other people working on their own copies of the code, and it is possible that I will find time to do so again once the new financial year starts. The last thing any of us would want is duplication of effort. In your new design, have you considered the cacheing issues that Keith I discussed recently? Regards, Dave. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
