On Saturday 17 September 2005 21:40, Dan Nelson wrote:
> In the last episode (Sep 17), Christian Parpart said:
> > On Saturday 17 September 2005 08:34, Gleb Paharenko wrote:
> > > mysql> show create table ui\G;
> > >
> > > Table: ui
> > > Create Table: CREATE TABLE `ui` (
> > > `uuid()` varchar(36)
In the last episode (Sep 17), Christian Parpart said:
> On Saturday 17 September 2005 08:34, Gleb Paharenko wrote:
> > mysql> show create table ui\G;
> >
> > Table: ui
> > Create Table: CREATE TABLE `ui` (
> > `uuid()` varchar(36) NOT NULL default ''
>
> I've been testing your example as I feel re
Hello.
The data type should be VARCHAR(36) as it was in my example. There
is a bug in some versions. See:
http://bugs.mysql.com/bug.php?id=13290
Christian Parpart <[EMAIL PROTECTED]> wrote:
>
> I've been testing your example as I feel really much safer with UUIDs instead
> of aut
On Saturday 17 September 2005 08:34, Gleb Paharenko wrote:
> mysql> show create table ui\G;
>
> *** 1. row ***
>
> Table: ui
>
> Create Table: CREATE TABLE `ui` (
>
> `uuid()` varchar(36) NOT NULL default ''
I've been testing your example as I feel r
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 ***
Hi all,
Im researching switching a production database system to use UUID's instead of
AUTO_INCREMENT columns for various ids. I've looked at various MySQL
documentation, and it seems to be what i want.
This change will really affect 2 separate database servers. Both are using
InnoDB tables. O
