[pgadmin-hackers] SVN Commit by dpage: r6737 - trunk/www/download
Author: dpage Date: 2007-10-12 09:50:55 +0100 (Fri, 12 Oct 2007) New Revision: 6737 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6737&view=rev Log: Remove dead link. Modified: trunk/www/download/rpm.php ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [pgadmin-hackers] pgAdmin licence
Andreas Pflug wrote: > No. You removed VC6 support, which was absolutely vital for me, without > ever asking whether that was viable. Since my development was tightly > integrated, I wasn't able to switch one of projects separately (at least > in the timeframe available). Oh, I'm sorry - I thought it was the wxGrid thing you objected to. WRT to moving to VC++ 2005, I *did* ask your opinion (and even stated 'and drop VC++6 support'), and the only objection you raised was that you thought we'd have to link with the .NET runtimes which I investigated and found was not the case. The thread is here: http://archives.postgresql.org/pgadmin-hackers/2006-04/msg00054.php Regardless, if you needed to retain VC++ 6.0 support for compatibility with your private work, surely it would have been infinitely easier to just maintain your own project file, rather than forking and having to duplicate all the effort to keep up to date with new PostgreSQL releases? > Yes, but not the query tool nor any of its helper classes. The base > classes however are reused by several other projects, including pgImport. As far as I can see, that puts you in breach of our licence as the distribution you posted a link to on your PSE Consulting website (www.pse-consulting.de/pg/pgImport.zip) includes *only* a zipped executable and no sign of any of the requirements of the pgAdmin licence. Much of the base class code in pgAdmin was written or modified by me (particularly the connection and recordset classes) and therefore cannot be claimed as your own original work. Please rectify this oversight immediately. Regards, Dave ---(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
[pgadmin-hackers] SVN Commit by dpage: r6738 - trunk/pgadmin3/pgadmin/schema
Author: dpage Date: 2007-10-12 10:29:12 +0100 (Fri, 12 Oct 2007) New Revision: 6738 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6738&view=rev Log: Guard against checking the server version if we're not connected. Modified: trunk/pgadmin3/pgadmin/schema/pgDatabase.cpp ---(end of broadcast)--- TIP 6: explain analyze is your friend
[pgadmin-hackers] SVN Commit by dpage: r6743 - trunk/pgadmin3/pgadmin/dlg
Author: dpage Date: 2007-10-12 17:03:24 +0100 (Fri, 12 Oct 2007) New Revision: 6743 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6743&view=rev Log: Prevent characters being incorrectly stripped from foreign key column names, per Alexander Kirpa Modified: trunk/pgadmin3/pgadmin/dlg/dlgForeignKey.cpp ---(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
[pgadmin-hackers] SVN Commit by guillaume: r6741 - in trunk/pgadmin3/pgadmin: dlg schema
Author: guillaume Date: 2007-10-12 15:47:33 +0100 (Fri, 12 Oct 2007) New Revision: 6741 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6741&view=rev Log: Fix the tablespace issue on index and indexconstraint. Modified: trunk/pgadmin3/pgadmin/dlg/dlgIndex.cpp trunk/pgadmin3/pgadmin/dlg/dlgIndexConstraint.cpp trunk/pgadmin3/pgadmin/schema/pgIndex.cpp trunk/pgadmin3/pgadmin/schema/pgIndexConstraint.cpp ---(end of broadcast)--- TIP 6: explain analyze is your friend
[pgadmin-hackers] SVN Commit by guillaume: r6739 - trunk/pgadmin3/i18n/fr_FR
Author: guillaume Date: 2007-10-12 14:57:06 +0100 (Fri, 12 Oct 2007) New Revision: 6739 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6739&view=rev Log: Fix french translation, per S?\195?\169bastien Lardi?\195?\168re. Modified: trunk/pgadmin3/i18n/fr_FR/pgadmin3.mo trunk/pgadmin3/i18n/fr_FR/pgadmin3.po ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [pgadmin-hackers] Handling the pg_global of tablespace.
Hiroshi Saito wrote: > From: "Dave Page" <[EMAIL PROTECTED]> > >> It should still work for superusers though shouldn't it? >> > > Eh?, Is it ACL bug of PostgreSQL ver 8.3b1? > > As for superuser, > 2007-10-11 13:53:23 ERROR : ERROR: permission denied for tablespace > pg_global Yes, I specifically asked Tom about the superuser case and he responded: http://archives.postgresql.org/pgsql-hackers/2007-08/msg01018.php I've reported the problem to pgsql-hackers with the relevant posts. /D ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [pgadmin-hackers] RC1 crashes when right clicked on template0
Devrim GÜNDÜZ wrote: > Hi, > > I thought this was fixed already, but this is what I got in Rc1: > > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread -1208342000 (LWP 30701)] > 0x080bc8b2 in pgConn::BackendMinimumVersion () Gah - thanks. Fixed. /D ---(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 guillaume: r6740 - in trunk/pgadmin3/pgadmin: dlg schema
Author: guillaume Date: 2007-10-12 15:34:30 +0100 (Fri, 12 Oct 2007) New Revision: 6740 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6740&view=rev Log: Check the PostgreSQL release before adding tablespace query, per reports from Albin Blaschka and Ariel R. Giomi. Modified: trunk/pgadmin3/pgadmin/dlg/dlgTable.cpp trunk/pgadmin3/pgadmin/schema/pgTable.cpp ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[pgadmin-hackers] SVN Commit by dpage: r6742 - in trunk/pgadmin3: . pgadmin/agent
Author: dpage Date: 2007-10-12 16:38:59 +0100 (Fri, 12 Oct 2007) New Revision: 6742 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6742&view=rev Log: Avoid using a correlated subquery that Greenplum doesn't support, per report from Jon Roberts. Modified: trunk/pgadmin3/CHANGELOG trunk/pgadmin3/pgadmin/agent/pgaJob.cpp ---(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
Re: [pgadmin-hackers] pgAdmin licence
Dave Page wrote: > Andreas Pflug wrote: > > >> No. You removed VC6 support, which was absolutely vital for me, without >> ever asking whether that was viable. Since my development was tightly >> integrated, I wasn't able to switch one of projects separately (at least >> in the timeframe available). >> > > Oh, I'm sorry - I thought it was the wxGrid thing you objected to. > > WRT to moving to VC++ 2005, I *did* ask your opinion (and even stated > 'and drop VC++6 support'), and the only objection you raised was that > you thought we'd have to link with the .NET runtimes which I > investigated and found was not the case. > > The thread is here: > http://archives.postgresql.org/pgadmin-hackers/2006-04/msg00054.php > > Regardless, if you needed to retain VC++ 6.0 support for compatibility > with your private work, surely it would have been infinitely easier to > just maintain your own project file, rather than forking and having to > duplicate all the effort to keep up to date with new PostgreSQL releases? > > >> Yes, but not the query tool nor any of its helper classes. The base >> classes however are reused by several other projects, including pgImport. >> > > As far as I can see, that puts you in breach of our licence as the > distribution you posted a link to on your PSE Consulting website > (www.pse-consulting.de/pg/pgImport.zip) includes *only* a zipped > executable and no sign of any of the requirements of the pgAdmin > licence. Much of the base class code in pgAdmin was written or modified > by me (particularly the connection and recordset classes) and therefore > cannot be claimed as your own original work. > I don't think so. It was me who invented the db base classes, besides they have undergone some major rewrite (ever heard of pgSetIterator?) I checked quite thoroughly, including the icon (which I'd replace if I had another one at hand). Regards, Andreas ---(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
Re: [pgadmin-hackers] pgAdmin licence
Andreas Pflug wrote: >> > I don't think so. It was me who invented the db base classes, besides > they have undergone some major rewrite (ever heard of pgSetIterator?) > I checked quite thoroughly, including the icon (which I'd replace if I > had another one at hand). You invented the abstraction, but taking pgConnBase as an example, pgConnBase::pgConnBase, pgConnBase::ExecuteVoid, pgConnBase::ExecuteScalar, pgConnBase::ExecuteSet were all copied from pgConn and were the key member functions originally written by Mark Yeatman and myself. Similarly, pgSetBase was largely ripped from pgSet, base.cpp includes numerous functions from misc.cpp, appbase.cpp includes a small amount of code from pgAdmin3.cpp. I can easily trace back significant amounts of code in those base classes to times before you submitted *any* patches, to commits by Mark and I (as can anyone will to spend a few minutes at http://svn.pgadmin.org/). The only base class that originated from you was factory.cpp, and even that contains code written by Magnus Hagander and I committed long before you left the project. I do not for one minute deny that you also have contributed significant code to those classes, but the fact remains all bar the factory code is derived from the work of others, no matter how rewritten it has become in your work. Given that on your PSE Consulting website at http://www.pse-consulting.de/os.html you speak of how you appreciate the Open Source concept, I find it incredible that you can have such disregard for the hard work of others by ignoring the very basic principles of Open Source. I'm dismayed that someone I considered a friend and held in high regard could act in such a disgraceful manner. Regards, Dave. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] pgAdmin licence
Dave, since pgImport was originally written to import from file to MSSQL, with pgsql support added later (and pgConnection/pgSet never supported COPY), you're trying to see stuff that's not there (nor is factory.cpp). Regards, Andreas ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [pgadmin-hackers] pgAdmin licence
> --- Original Message --- > From: Andreas Pflug <[EMAIL PROTECTED]> > To: Dave Page <[EMAIL PROTECTED]> > Sent: 12/10/07, 22:11:36 > Subject: Re: pgAdmin licence > > Dave, > since pgImport was originally written to import from file to MSSQL, with > pgsql support added later (and pgConnection/pgSet never supported COPY), > you're trying to see stuff that's not there (nor is factory.cpp). > So when you said: > The base classes however are reused by several other projects, including > pgImport. were you making it up? If you are not using pgAdmin code in your closed source projects, why was it such a problem when the pgAdmin project files were upgraded which, as you said, broke your other private code? Regards, Dave ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
