At 01:36 6/08/2002 -0700, Blake wrote:
I'm no SQL expert, but isn't that what database sequences are for?
Yes, but the code in pipe.c is at a lower level - I think. One solution
would be to use the DB to allocate a number (eg. db_get_unique_id).
Or, depending on how pipe.c is used (eg. as long as it is not forked), we
could just append a sequence number.
But, AFAICT, the current code does not produce unique IDs.
Philip Warner wrote:
At 18:05 6/08/2002 +1000, Philip Warner wrote:
Looking at the code in pipe.c, it uses the current time to build the ID;
several messages were received within a second of each other - hence the
non-unique ID.
_______________________________________________
Dbmail mailing list
Dbmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
