Hi Petr.. Thanks for the replies..
In my case, the ID is used to store a generated uuid, as a completely unique string. The overall process, is that I have multiple systems, and they each run a local process, with a local db/tbl structure.. I then reconcile all the processes on a centralized mysql db process at a later time.. My process enforces that the ID is essentually unique across all my systems. I don't want to change this approach. Nor do I simply want to have an ID that's an int, simply to use SQLObject... So.. my goal is to be able to use sqlobject to interface with the existing mysql db/tbl, and to be able to modify/handle an id that's a string... thanks!!! I don't want to -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Petr Jakeš Sent: Sunday, December 30, 2007 1:06 PM To: bruce Cc: sqlobject-discuss@lists.sourceforge.net Subject: Re: [SQLObject] sqlobject - python question/issue One more thing. If it is possible I strongly recommend to use ID which has "no meaning" and the best choice is an integer of course!!! (Try to find somes articles about IDs etc. on the web) So using automaticaly generated IDs (it does not matter if it is generated by your code or by SQLobject) is highly recommended. Petr ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss