Hello.
I'm not sure, but in most cases we should trust MySQL. Use this trick :)
mysql> create table ui select uuid();
Query OK, 1 row affected (0.01 sec)
Records: 1 Duplicates: 0 Warnings: 0
mysql> show create table ui\G;
*************************** 1. row ***************************
Table: ui
Create Table: CREATE TABLE `ui` (
`uuid()` varchar(36) NOT NULL default ''
sean c peters <speters@stripped> wrote:
> Hi all,=20
> Im researching switching a production database system to use UUID's instead=
> of=20
> AUTO_INCREMENT columns for various ids. I've looked at various MySQL=20
> documentation, and it seems to be what i want.=20
> This change will really affect 2 separate database servers. Both are using=
> =20
> InnoDB tables. One is running MySQL 4.1.3-beta on solaris, and the other is=
> =20
> running 4.1.8-Max on Redhat Linux.=20
>
> =46rom what i've been reading, the only thing i cant determine is what colu=
> mn=20
> type to use to store the UUID's. These will be foreign keys between some=20
> tables, and the unique ids in all tables for this system.=20
>
> Should i be using BINARY() columns ?
>
> Thanks much
>
> =2D-=20
> Sean Peters
> Senior Programmer, WIREData Inc.
> speters@stripped
>
> "The software required Windows 2000 or better, so i Downloaded Linux"
>
>
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ Gleb.Paharenko@stripped
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
<___/ www.mysql.com
