You need a guaranteed unique id to be used as a primary index field.
"Need" is a strong word. Its very deployment and use-case sensitive.
In the case of a database, it is a hard requirement. A primary index field must be guaranteed unique. There is absolutely no way around this issue.
"Need"? No. It is a deployment choice with easily understood ramifications.
Perhaps for the application, but this is a totally different ballgame when it comes to a database. Google for "primary index field", and hopefully you will understand.
-- Brad Knowles, <[EMAIL PROTECTED]>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)
_______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
