Jan Wieck wrote:
> Christopher Kings-Lynne wrote:
> >
> > > 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
Christopher Kings-Lynne wrote:
>
> > 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
> 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 need
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 ca
> > > > Changing data types probably won't appear. I don't know of anyone
> > > > working on it -- and it can be quite a complex issue to get a good
> > > > (resource friendly and transaction safe) version.
> > >
> > > I'd be happy with a non-resource friendly and non-transaction-safe version
> >
On Wed, 10 Jul 2002, Tom Lane wrote:
> Bradley Baetz <[EMAIL PROTECTED]> writes:
> > I'm referring to the mysql |timestamp| type, which will update that
> > column's contents to |now()| when any UPDATE is given for that partcular
> > row, unless the column was assigned to. I don't know how to han
Bradley Baetz <[EMAIL PROTECTED]> writes:
> I'm referring to the mysql |timestamp| type, which will update that
> column's contents to |now()| when any UPDATE is given for that partcular
> row, unless the column was assigned to. I don't know how to handle the
> last part in a trigger.
It'd probab
On Thu, 11 Jul 2002, Christopher Kings-Lynne wrote:
> Of course, you might have thought about the correct column types in advance,
> but hey :) I think that there's no way to have a rollback-able column type
> change without temporarily doubling space. Actually, I think Oracle has
> some sort o
On 10 Jul 2002, Rod Taylor wrote:
> enum(A,B,C) -> column char(1) check (column IN ('A', 'B', 'C'))
right.
>
> timestamp? Output pattern may be different, but PostgreSQL 7.3 will
> accept any timestamp I've thrown at it. Lots of weird and wonderful
> forms.
I'm referring to the mysql |times
> > > Changing data types probably won't appear. I don't know of anyone
> > > working on it -- and it can be quite a complex issue to get a good
> > > (resource friendly and transaction safe) version.
> >
> > I'd be happy with a non-resource friendly and
> non-transaction-safe version
> > over not
> > Note that before bugzilla really supports postgresql, we (ie
> the bugzilla
> > team) are going to need DROP COLUMN support, as well as support for
> > changing a field's type. This is because thats how upgrades are
> done, when
> > new features change the bz schema.
>
> DROP COLUMNS should be
Bradley Baetz wrote:
>
>
> Note that before bugzilla really supports postgresql, we (ie the bugzilla
> team) are going to need DROP COLUMN support, as well as support for
> changing a field's type. This is because thats how upgrades are done, when
> new features change the bz schema.
DROP COLUM
On 10 Jul 2002, Rod Taylor wrote:
> > However, is there an easy way of obtaining the list of columns (and their
> > types/indexes/etc) in a table, so that we can recreate table a with just
> > that column missing? One which won't break when the underlying pg_* schema
> > changes?
>
> I see. No
On 10 Jul 2002, Rod Taylor wrote:
> On Wed, 2002-07-10 at 19:44, Bradley Baetz wrote:
> >
> >
> > Note that before bugzilla really supports postgresql, we (ie the bugzilla
> > team) are going to need DROP COLUMN support, as well as support for
> > changing a field's type. This is because thats
Note that before bugzilla really supports postgresql, we (ie the bugzilla
team) are going to need DROP COLUMN support, as well as support for
changing a field's type. This is because thats how upgrades are done, when
new features change the bz schema.
See
http://lxr.mozilla.org/mozilla/source/
Iavor,
> Any other suggestions?
I can tell you from experience that Double-Choco-Latte, another
PHP/PostgreSQL tool, is really set up just for single projects. So it
would work fine for PGAccess-only. However, DCL has its own problems
and is not necessarily better than Mozilla; I personally d
On Wed, 2002-07-10 at 21:49, Iavor Raytchev wrote:
> Josh Berkus said:
> > Iavor,
> >
> >> Any other suggestions?
> >
> > I can tell you from experience that Double-Choco-Latte, another
> > PHP/PostgreSQL tool, is really set up just for single projects. So it
> > would work fine for PGAccess-only
Josh Berkus said:
> Iavor,
>
>> Any other suggestions?
>
> I can tell you from experience that Double-Choco-Latte, another
> PHP/PostgreSQL tool, is really set up just for single projects. So it
> would work fine for PGAccess-only. However, DCL has its own problems
> and is not necessarily bett
> > 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/g
MAIL PROTECTED]>;
"pgsql-interfaces" <[EMAIL PROTECTED]>
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 -
> &g
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 reques
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.
22 matches
Mail list logo
