RE: [pgadmin-hackers] problem compilation pgadmin2
> > > > -Original Message- > > From: frank_lupo [mailto:[EMAIL PROTECTED] > > Sent: 03 April 2003 08:04 > > To: pgadmin-hackers > > Subject: [pgadmin-hackers] problem compilation pgadmin2 > > > > > > Hi Dave > > > > > > > > Ok finally they are successful to use cvs. > > > > I have download the pgadmin2, pgschema and activex. > > > > When I execute the compilation using BuildAll.bat, proposals > > of the errors come me. > > > > > > > > Impossible to set up the compatible component with the > > version: c:\pgadmin2\binaries\pgschema.dll. > > > > This error is present in all the programs. > > > > > > > > The compilation does not come executed. > > > > How I can make in order to resolve the problem? > > Hi Frank, > > Copy an old version of pgschema.dll to > c:\pgadm in2\bina r ies\pgschema.dll. It's just the compiler complaining > that it can't find the version with the existing class ids etc. > > Regards, Dave. > Hi Dave Ok, the compilation is ok. The file that I have download with cvs I have them in single reading. It is right that they are therefore? Bye !! Frank Lupo (Wolf) !! /\_ _/\ \ o o / --ooo-ooo--- -- Prendi GRATIS l'email universale che... risparmia: http://www.email.it/f Sponsor: Moda sport ai tuoi piedi! La scarpa di tendenza del momento la trovi da Oliviero.it Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=1077&d=3-4 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-hackers] problem compilation pgadmin2
> -Original Message- > From: frank_lupo [mailto:[EMAIL PROTECTED] > Sent: 03 April 2003 08:04 > To: pgadmin-hackers > Subject: [pgadmin-hackers] problem compilation pgadmin2 > > > Hi Dave > > > > Ok finally they are successful to use cvs. > > I have download the pgadmin2, pgschema and activex. > > When I execute the compilation using BuildAll.bat, proposals > of the errors come me. > > > > Impossible to set up the compatible component with the > version: c:\pgadmin2\binaries\pgschema.dll. > > This error is present in all the programs. > > > > The compilation does not come executed. > > How I can make in order to resolve the problem? Hi Frank, Copy an old version of pgschema.dll to c:\pgadmin2\binaries\pgschema.dll. It's just the compiler complaining that it can't find the version with the existing class ids etc. Regards, Dave. ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[pgadmin-hackers] problem compilation pgadmin2
Hi Dave Ok finally they are successful to use cvs. I have download the pgadmin2, pgschema and activex. When I execute the compilation using BuildAll.bat, proposals of the errors come me. Impossible to set up the compatible component with the version: c:\pgadmin2\binaries\pgschema.dll. This error is present in all the programs. The compilation does not come executed. How I can make in order to resolve the problem? Bye !! Frank Lupo (Wolf) !! /\_ _/\ \ o o / --ooo-ooo--- -- Prendi GRATIS l'email universale che... risparmia: http://www.email.it/f Sponsor: Destinazione Scandinavia a soli 80 Euro...clicca e scopri la convenienza Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=1226&d=3-4 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[pgadmin-hackers] PGA3 Operator Question
Dave et al, * This is a temporary solution until the cache is built. I need to get a list of operators from the database that will return only booleans types, not integer types. This is basically a list of possible "join" operators. This is the query I've found works the best. Do namespaces matter here? Can anybody suggest a better query? SELECT DISTINCT a.oprname FROM pg_operator a JOIN pg_type b on ( a.oprresult = b.oid ) WHERE a.oprkind = 'b' and b.typname = 'bool' ORDER BY a.oprname -Keith ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] pgadmin3 query tools
Andreas, > >That's old code. It's been namespaced for more than a month. > > I just committed the changes that deal with that. Go ahead and update. Also there is a bit more functionality on the QueryBuilder. I'll be spending most of the day finishing up what I started. It should be mostly done by the end of today (unless the coffee wears off). > Look at pgTable::GetSql(), there I browse, force pgCollections to > populate and update pgColumns. It's easy, and could be done from > PG_TABLES as well. > Calling ShowTreeDetails(browser,0,0,0,0) has virtually no cost after the > first call. Good to know. > That's totally impossible. A long time ago, I decided to write error > free code. Since then, my code has been proven to be complete, precise, > delicious, juicy, absolutely genious and defect free. > Well, almost... ;-) :) It must have a been some M*cr*s*ft conspirator. > Just tell me where you find something. And I'll find out who's at my > machine adding that leaks while I'm off-site. Just reviewed all > ExecuteSet and found two missing pgSet deletes in pgColumn and > pgSequence. I can't find them now, so I'm guessing the missing deletes cleared them up. -Keith ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] Qeustion pgadmin2 develop
Le Mercredi 2 Avril 2003 14:54, Dave Page a écrit : > What do you (and Mark, Jean-Michel, Keith, Andreas - and anyone else I > forgot) think? Dear friends, I don't have many things to say as I am not a contributor to pgAdmin3. pgAdmin3 seems to be the future... You are doing a great job, I whish to join sooner or later and participate. Cheers, Jean-Michel POURE ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-hackers] Qeustion pgadmin2 develop
frank_lupo wrote: Hi Dave There are many new functionalities for pgadmin2 that I would want to develop. I wonder if it has sense to make them or of it it is worth the pain. How much time will want that the pgadmin3 before to us usable? I see that the development and much assets. What I must make? Frank, I've seen a lot of traffic in this list regarding pgadmin2 features over the last time, but I didn't look any further into it. My focus was towards a query tool (weakness in pgadmin2) and a good schema browser (cannot be made better, thus simply recoded). So I don't know what your extentions do. I believe they all are some kind of wizards, implemented as plugin. I wonder if these plugins could be integrated into pgadmin3 too, using automation. This would immediately make all pga2 plugins available to pga3-w32 users. Later on, they could be recoded 1:1 in C++. On the other hand, it's no real fun to use VB from C++, and as I think about it further the database connection probably will be a problem since pga2 uses ADO, while pga3 avoids this. Only recoded plugins possible, I'm afraid. With regard to Dave's timeframe mentioned, I can say that for my needs pgadmin3 is sufficient. I believe there are many programmers that could benefit from using pgadmin3 as it is right now. At least, I released it to some people that used to use ISQL on MSSQL, and switch over to PostgreSQL right now. Anyway, I might find some time to implement some/many/most/all of the missing property/create dialogs, bringing us some steps further. So maybe we reach pga2-1.2 much earlier. Dave, maybe it makes sense to create a release plan stating which version of pgadmin3 should include which features. As you might have noticed, pgadmin3 VERSION states V 0.1.0 at the moment, indicating "many things to come". Regards, Andreas ---(end of broadcast)--- TIP 3: 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
Re: [pgadmin-hackers] pgadmin3 query tools
Dave Page wrote: Yup, certainly is. BTW, did you know that thanks to Frank Lupo, pga2 fully supports Casts and Conversions in the schema now? OK, message understood. CAST, CONVERSION and OPERATOR CLASS are missing in pgadmin3 (yet). Any more objects of your desire? Centerfolds excepted. Regards, Andreas ---(end of broadcast)--- TIP 3: 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
Re: [pgadmin-hackers] Qeustion pgadmin2 develop
Hi Frank, It's rumoured that frank_lupo once said: > Hi Dave > > There are many new functionalities for pgadmin2 that I would want to > develop. I wonder if it has sense to make them or of it it is worth > the pain. How much time will want that the pgadmin3 before to us > usable? > I see that the development and much assets. > What I must make? This is something that is of concern to me. pga2 is by no means useless or at a dead-end, yet I want to concentrate on pga3 as it will allow us to go cross platform, and handle Unicode - 2 very popular requests which are seriously hindering pga2 pgAdmin 3 is a fair way from being usable, not least because I have so little time at the moment. On the other hand, Andreas and Keith have both been working hard. Realistically, I think it is likely to be 3 - 6 months before pga3 has the features of pga2 v1.2. So, I am happy to do a 1.6 release of pga2 seeing as you have put in so much effort with useful new features. I will leave it up to you to decide when you have done enough now - just let me know and I'll look at doing a beta release. In the long term, if you know C++, it would be great to have your input on pga3. What do you (and Mark, Jean-Michel, Keith, Andreas - and anyone else I forgot) think? Regards, Dave. ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] pgadmin3 query tools
It's rumoured that Andreas Pflug once said: > Exactly. I've seen quite a lot of querying tools, and most of them were > quite ugly and at the edge of usability. For my experience, I think > two tool windows are the easiest way to handle it, not only in > concerning coding, but also regarding user handling. The best tool > I've been working with was MSSQL2000's ISQLW, which does use separate > windows for editing and arbitrary query output. And pgadmin3 is going > to be better, because its schema representation is better. Yup, certainly is. BTW, did you know that thanks to Frank Lupo, pga2 fully supports Casts and Conversions in the schema now? > For a programmer, acceptance stands and falls by the tools. We are on > the way to supply a tool that leaves virtually no wishes. Let's show > those big companies that open software is better! Who needs O.., who > needs M..., we got PostgreSQL! Damn straight!! :-) Regards, Dave. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[pgadmin-hackers] Qeustion pgadmin2 develop
Hi Dave There are many new functionalities for pgadmin2 that I would want to develop. I wonder if it has sense to make them or of it it is worth the pain. How much time will want that the pgadmin3 before to us usable? I see that the development and much assets. What I must make? Bye !! Frank Lupo (Wolf) !! /\_ _/\ \ o o / --ooo-ooo--- -- Prendi GRATIS l'email universale che... risparmia: http://www.email.it/f Sponsor: Hai bisogno di un nuovo decoder per guardare le partite della tua squadra del cuore? Trovalo qui! Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=765&d=2-4 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] pgadmin3 query tools
Dave Page wrote: So you're saying we make the arbitrary query tools (SQL/QB) produce very fast, but read-only output, but add an 'Edit' option for tables/views, that allows editting of their contents an a purpose designed grid? That would certainly be easier to code as we would always know the base structure of what we were editting... Exactly. I've seen quite a lot of querying tools, and most of them were quite ugly and at the edge of usability. For my experience, I think two tool windows are the easiest way to handle it, not only in concerning coding, but also regarding user handling. The best tool I've been working with was MSSQL2000's ISQLW, which does use separate windows for editing and arbitrary query output. And pgadmin3 is going to be better, because its schema representation is better. We got different recommendations, so we need different tools. If we try to put all into one, we get only second best. And you will agree, pgsql is worth only the best. Absolutely. For a programmer, acceptance stands and falls by the tools. We are on the way to supply a tool that leaves virtually no wishes. Let's show those big companies that open software is better! Who needs O.., who needs M..., we got PostgreSQL! Regards, Andreas ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-hackers] pgadmin3 query tools
It's rumoured that Andreas Pflug once said: > Actually, I see YAQT (yet another query tool) for editing a table. You > just pick a table (maybe view), hit "Edit" and scroll up and down in > there. It must be capable of unlimited rows, which isn't easy but can > be done (I already implemented something like that in earlier days). > And it should have inline editing, feels better than the current > pgadmin2 solution. So you're saying we make the arbitrary query tools (SQL/QB) produce very fast, but read-only output, but add an 'Edit' option for tables/views, that allows editting of their contents an a purpose designed grid? That would certainly be easier to code as we would always know the base structure of what we were editting... > We got different recommendations, so we need different tools. If we try > to put all into one, we get only second best. And you will agree, > pgsql is worth only the best. Absolutely. Regards, Dave. ---(end of broadcast)--- TIP 3: 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
Re: [pgadmin-hackers] pgadmin3: present and future
It's rumoured that Andreas Pflug once said: > Dave Page wrote: > >>That's alright. Tom Lane explained why it wouldn't work in the backend >>anyway... >> >>Regards, Dave. >> >> >> > Dave, > > maybe you got me wrong. > The CODING is already done... :-) No, I understood. I meant that it's OK you worked on it because Tom thought we had to do it that way. Though it now seems a possibility to add a new version of pg_get_viewdef(), which I might try to look at. But that's for another day... :-) /D ---(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] pgadmin3 query tools
Dave Page wrote: That's fine with me. My major concern is that the code that drives the grid is only written once. This is likely to get quite complex once editting features are added, and I don't want to maintain 2 copies. I always want to keep the look and feel consistant. So, how about we create a class derived from the wxNotebook as Andreas suggests, which can just be passed the completed query to display the results and allow editting thereof (where possible), and display explain output (and hopefully one day we can add a visual explain tab). Hi, I don't think it's a good idea trying to inject editing features in the current wxListView. Actually, my first implementation used wxGrid, but was a real pain for bigger result sets. SELECT * from pg_attribute (200 rows) wouldn't complete within 30 seconds, and the destruction of a 2000 row grid (without data) would consume several seconds! From that times, we got that split elapsed seconds display to see how the time splits between query execution and result retrieval. Actually, I see YAQT (yet another query tool) for editing a table. You just pick a table (maybe view), hit "Edit" and scroll up and down in there. It must be capable of unlimited rows, which isn't easy but can be done (I already implemented something like that in earlier days). And it should have inline editing, feels better than the current pgadmin2 solution. We got different recommendations, so we need different tools. If we try to put all into one, we get only second best. And you will agree, pgsql is worth only the best. Regards, Andreas ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] pgadmin3: present and future
Dave Page wrote: That's alright. Tom Lane explained why it wouldn't work in the backend anyway... Regards, Dave. Dave, maybe you got me wrong. The CODING is already done... :-) Regards, Andreas ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-hackers] pgadmin3: present and future
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 01 April 2003 22:47 > To: Dave Page; [EMAIL PROTECTED] > Subject: Re: [pgadmin-hackers] pgadmin3: present and future > > > Dave Page wrote: > > >This would *definately* be easier to implement in PostgreSQL > >at the thought of writing another SQL parser>. I'll post a > message to > >the hackers list... > > > >Regards, Dave. > > > > > > > Too late, > already done (at least a 96% solution). That's alright. Tom Lane explained why it wouldn't work in the backend anyway... 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] pgadmin3 query tools
Hi guys, > -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 02 April 2003 01:50 > To: [EMAIL PROTECTED] > Subject: Re: [pgadmin-hackers] pgadmin3 query tools > > >Here are my two cents. We put a "view" menu in BOTH our > tools. > That's not far from my solution, switching from one to the > other with a > menu/toolbar. We would have two tools, I wouldn't really bother about > that. As I wrote, the core code could be wrapped into a > control, either > derived from wxNotebook or wxListView, whatever is more > useful. That's fine with me. My major concern is that the code that drives the grid is only written once. This is likely to get quite complex once editting features are added, and I don't want to maintain 2 copies. I always want to keep the look and feel consistant. So, how about we create a class derived from the wxNotebook as Andreas suggests, which can just be passed the completed query to display the results and allow editting thereof (where possible), and display explain output (and hopefully one day we can add a visual explain tab). There might be another argument towards two distinct > tools: Porting to > **ix might be easier. The biggest problem we're finding in *nix is that the ctor for wxString doesn't like taking an initial value (iirc). Mark, I know you're busy, but if you get 5 minutes, can you do an update and try rebuilding on Linux please? It's possible that there are one or two source files missing from the Makefile... > Just tell me where you find something. And I'll find out who's at my > machine adding that leaks while I'm off-site. Just reviewed all > ExecuteSet and found two missing pgSet deletes in pgColumn > and pgSequence. Ahh, those pesky code pixies Regards, Dave. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
