php-db | 2001011
Date: 01/15/01
- Next message: William Bailey: "[PHP-DB] Storeing images in a database table, should it be done?"
- Previous message: Miguel Loureiro: "[PHP-DB] user choices Vs infoDB ???"
- In reply to: Cahyo S. Aji: "[PHP-DB] ENUM type"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Greetings, Cahyo!
At 15.01.01, 18:47, you wrote:
CSA> I don't know what is the benefit if we use ENUM type.
CSA> can everybody explain it?
It is an ugly crutch.
Well, you see, most RDBMSes will allow you to make a 'lookup
table' or 'dictionary' or something (dunno its official name).
Something like:
CREATE TABLE foo_baz_dictionary (
baz integer not null primary key,
baz_name char(50)
);
-- baz is a potential "enum" field
CREATE TABLE foo (
bar integer,
...
baz integer,
foreign key (baz) references foo_baz_dictionary
);
Then when you insert something into 'foo', its 'baz' field is checked
against foo_baz_dictionary (which is far more manageable
than ENUM field definition).
MySQL does not support foreign keys and so its creators came up with ENUM
solution.
-- Yours, Alexey V. Borzov, Webmaster of RDW-- PHP Database Mailing List (http://www.php.net/) To unsubscribe, e-mail: php-db-unsubscribe <email protected> For additional commands, e-mail: php-db-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: William Bailey: "[PHP-DB] Storeing images in a database table, should it be done?"
- Previous message: Miguel Loureiro: "[PHP-DB] user choices Vs infoDB ???"
- In reply to: Cahyo S. Aji: "[PHP-DB] ENUM type"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

