Thread: bugzilla.pgaccess.org
Hello,
As of today, a Bugzilla has been made available at -
bugzilla.pgaccess.org
This is a pretty straight forward installation of Bugzilla 2.14.2
It is currently empty. There are even no components so the first bug
submissions can be either request for components or have to wait a few days.
As we do not have much experience setting Bugzila for open source project
(we use it for internal projects - with groups and permissions), all
comments are welcome.
Iavor
--
Iavor Raytchev
very small technologies (a company of CEE Solutions)
in case of emergency -
call: + 43 676 639 46 49
or write to: support@verysmall.org
www.verysmall.org
Iavor Raytchev wrote: > > Hello, > > As of today, a Bugzilla has been made available at - > > bugzilla.pgaccess.org > > This is a pretty straight forward installation of Bugzilla 2.14.2 > > It is currently empty. There are even no components so the first bug > submissions can be either request for components or have to wait a few days. > > As we do not have much experience setting Bugzila for open source project > (we use it for internal projects - with groups and permissions), all > comments are welcome. Just out of curiosity, what database is backing it? If it isn't PostgreSQL, what about using PHP BugTracker instead? That runs on top of PostgreSQL. http://sourceforge.net/projects/phpbt/ Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #
----- Original Message ----- From: "Jan Wieck" <JanWieck@Yahoo.com> To: "Iavor Raytchev" <iavor.raytchev@verysmall.org> Cc: "pgaccess - developers" <developers@pgaccess.org>; "pgaccess - users" <users@pgaccess.org>; "pgsql-hackers" <pgsql-hackers@postgresql.org>;"pgsql-interfaces" <pgsql-interfaces@postgresql.org> Sent: Tuesday, July 09, 2002 5:28 PM Subject: Re: [HACKERS] bugzilla.pgaccess.org > Iavor Raytchev wrote: > > > > Hello, > > > > As of today, a Bugzilla has been made available at - > > > > bugzilla.pgaccess.org > > > > This is a pretty straight forward installation of Bugzilla 2.14.2 > > > > It is currently empty. There are even no components so the first bug > > submissions can be either request for components or have to wait a few days. > > > > As we do not have much experience setting Bugzila for open source project > > (we use it for internal projects - with groups and permissions), all > > comments are welcome. > > Just out of curiosity, what database is backing it? > > If it isn't PostgreSQL, what about using PHP BugTracker instead? That > runs on top of PostgreSQL. > > http://sourceforge.net/projects/phpbt/ > > > Jan Or Gborg... ;-) http://gborg.postgresql.org/project/gborg/projdisplay.php Cheers, Ned
> How hard will the migration from MySQLzilla to PostgreSQLzilla be ? Is this a rhetoric question? I have no idea. A posting I saw (by one of the Bugzilla guys, I think) required something to be done in PostgreSQL before they can migrate - something exactly related to the issue of upgrading from one Bugzilla version to another. That means - Bugzilla takes care of the database upon upgrade. I am pretty sure somebody will write a migration tool. Otherwise the whole noise is somehow useless. Or not?
In reply to Hannu Krosing Iavor Raytchev wrote: > > > How hard will the migration from MySQLzilla to PostgreSQLzilla be ? > > Is this a rhetoric question? > > I have no idea. > > A posting I saw (by one of the Bugzilla guys, I think) required something to > be done in PostgreSQL before they can migrate - something exactly related to > the issue of upgrading from one Bugzilla version to another. I have included pgsql-hackers again, where this discussion originally started crossposted. Hannu's question is absolutely not rhetoric. I see a concern about using a MySQL based tool for PostgreSQL related project management on a public site in it. The Bugzilla project plans to support PostgreSQL in one of their future releases, but this requires functionality in PostgreSQL, that is not even scheduled for 7.3. So the availability of a supported PostgreSQL port of Bugzilla is unpredictable at this time. My opinion is that a project as closely related to PostgreSQL as pgaccess should try to use PostgreSQL backed management tools. The switch to PHP BugTracker or something else at this time would be easiest, since the Bugzilla installation on pgaccess.org is virgin and does not contain any data yet. This is reason why I suggested that switch when you asked for comments originally. And I have not yet seen any argument against it, nor any reason why to start off with a MySQL based Bugzilla version now. Especially when there are equivalent solutions using PostgreSQL available. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #
.. inside of each other using ECPG ? I have a situation where it would be advantages to open a cursor, retrieve a tuple, then open another query based on the results of the first. Then when that query has been processed return to the first query and get the second tuple. Is this possible ? cheers, Jim Parker
> The Bugzilla project plans to support PostgreSQL in one of their future > releases, but this requires functionality in PostgreSQL, that is not > even scheduled for 7.3. So the availability of a supported PostgreSQL > port of Bugzilla is unpredictable at this time. I think he said that they needed DROP COLUMN functionality, which is being worked on for 7.3. (Although I haven't had time to work on it for a few days) Chris
> Is this possible ?
Sure.
- Thomas