Tim

Is there a reason why / and \ aren't valid database name characters?

Roy Lambert

Roy,

Probably has to do with the fact that / and \ are not valid for file names
either.

Fons

"Roy Lambert" <roy.lambert@skynet.co.uk> schreef in bericht
news:C6254934-2478-443B-A86E-2CC745FC5FB2@news.elevatesoft.com...
> Tim
>
> Is there a reason why / and \ aren't valid database name characters?
>
> Roy Lambert

Fons


That was my first thought but database names are simply an entry in a database NOT subject to M$'s file system

Roy Lambert

Roy,

True... but I can't think of any other reason   Only Tim can...

Fons

Roy,

<< Is there a reason why / and \ aren't valid database name characters? >>

Identifiers are not categorized in EDB - the same set of valid characters is
used for all identifiers, and table identifiers are stored on disk in files
that use the same root name as the table name.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>Identifiers are not categorized in EDB - the same set of valid characters is
>used for all identifiers, and table identifiers are stored on disk in files
>that use the same root name as the table name.

I thought they were stored in the catalog?

Roy Lambert

Roy,

<< I thought they were stored in the catalog? >>

Sorry, I didn't quite word that right - yes, they are stored in the catalog,
but they are also used on disk for the table's physical file names.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


I think that adding that to the previous post I get it, but I've come up with a good strategy - I'll let ElevateDB tell me when I get it wrong.

Easy eh

Roy Lambert