Andrew Dunstan wrote:
You misunderstood me. I meant he wanted to make use of such a facility,
not that he wanted to build it.
Yeah, I had enough things on my plate just getting enums to work :)
By all means float ideas on this - the problem seems to me to be
ensuring that reservations are tim
Martijn van Oosterhout wrote:
Seems awfully complicated. The numbers don't mean anything, they don't
have to be contiguous. If you want to reduce the chance of conflict,
find a nice big block in unused_oids, add a random number between 0 and
100 and use that. Or squeeze yourself into a block tha
On Mon, Sep 18, 2006 at 10:09:52PM +0100, Tom Dunstan wrote:
> Hmm. A simpler way lessen the pain might be to have a script which could
> update OIDs in your catalog files. You'd have to run it BEFORE doing a
> merge. Ie, suppose I've allocated 2978-2991 in my patch, but since then
> OIDs have b
Gevik Babakhani wrote:
Actually, it would be nice to be able to reserve some. It would help
stop patch bitrot. I know Tom Dunstan wanted to do just that while he
was working on the enums patch.
Yes it would be very. If Tom Dunstan decided not to do that I would like
build such a thing.
On Mon, 2006-09-18 at 10:43 -0400, Andrew Dunstan wrote:
> Martijn van Oosterhout wrote:
> > On Mon, Sep 18, 2006 at 04:02:56PM +0200, Gevik Babakhani wrote:
> >
> >> I was wondering how one can avoid OID conflicts?
> >> I was testing the uuid patch on a new download from the CVS and
> >> I not
Martijn van Oosterhout wrote:
On Mon, Sep 18, 2006 at 04:02:56PM +0200, Gevik Babakhani wrote:
I was wondering how one can avoid OID conflicts?
I was testing the uuid patch on a new download from the CVS and
I noticed that some of the OIDs I thought to be free are used by someone
else :(
On Mon, 2006-09-18 at 16:32 +0200, Martijn van Oosterhout wrote:
> On Mon, Sep 18, 2006 at 04:02:56PM +0200, Gevik Babakhani wrote:
> > I was wondering how one can avoid OID conflicts?
> > I was testing the uuid patch on a new download from the CVS and
> > I noticed that some of the OIDs I thought
On Mon, Sep 18, 2006 at 04:02:56PM +0200, Gevik Babakhani wrote:
> I was wondering how one can avoid OID conflicts?
> I was testing the uuid patch on a new download from the CVS and
> I noticed that some of the OIDs I thought to be free are used by someone
> else :(
Not really. At the point of co
I was wondering how one can avoid OID conflicts?
I was testing the uuid patch on a new download from the CVS and
I noticed that some of the OIDs I thought to be free are used by someone
else :(
Any advice?
---(end of broadcast)---
TIP 1: if post
