Historically any form of punctuation, parameter delimiter, or filepath
delimiter in either a database name, field or column name, file or table
name would not be recommended; even if the RDBMS or File Handler allows it.
If you are able to stick to alphanumeric characters using underscores
characters if needed for clarity, you go a long way for portability across
various operating systems. Also, IPv4 addresses are readily converted to
single 32bit integers that minimize the need for dotted quartets.
Early versions of MySQL allowed periods. This caused OS incompatibility
issues. To my knowledge this was fixed prior to version 3 and you are no
longer allowed periods in database or table names. This, in my thinking, is
a good thing by assuring greater portability and easier migration.
I hope this helps.
SW Florida's First ISP
825 SE 47th Terrace
Cape Coral, FL 33904
----- Original Message -----
From: "Chance Ellis" <chance.ellis@stripped>
Sent: Wednesday, September 28, 2005 12:57 PM
Subject: Re: Table names with periods
Instead of criticizing people's designs without understanding the
requirements why don't you just answer the question, or don't you know
On 9/28/05, Martijn Tonies <m.tonies@stripped> wrote:
> >I am sure this has been asked before but I can't seemed to find it.
> > Canyou create table names with periods in them? I need to create tables
> >based on the IP address of machines (x.x.x.x)
> Ehm. Why?
> Instead of going the "silly table names" route, why not try a different
> With regards,
> Martijn Tonies
> Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
> Upscene Productions
> Database development questions? Check the forum!
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1