Do you wake up on the wrong side of the bed every morning?

Jerry Banker


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tony G
Sent: Friday, October 03, 2008 3:59 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] RE: spaces in file names

For reference, Windows still stores path/file names internally in
short 8.3 format.  Support for long names and additional
characters was added in Windows 95 as an abstraction (a view)
over that for common usage where non-technical people want to use
file names like:
   "J. Jones Budget, 2007-2008 (revised).doc"
   "Chelsea smashed! at homecoming '07.jpg"

Windows was designed to be an operating system for home users and
later became a server.  (Most people forget that "PC" stands for
"Personal Computer".)  Macintosh supported long, friendly
filenames back in 1984 for the same reasons.  Unix is a system
for engineers, not intended to be used by people creating
OS-level filenames for their docs or pictures.

Now, just to be clear, I didn't suggest that DBMS files should be
allowed to have spaces in them, like "CUSTOMER MASTER".  I was
giving IBM a little grief for not making use of a file system
enhancement which was added to Windows 13 years ago so that we
can put IBM programs under "Program Files".  There's no need for
*nix compatibility at this level, commands like uv, udt,
UniAdmin, and the UniSDK tools are all platform-specific,
OS-level programs, and have nothing to do with the data in the
DBMS.

It's almost understandable that paths to data may give the DBMS
grief if they contain spaces, like:
  D:\Data Sources\ABC Company\UV\Accounts\WAREHOUSE
But even in this case, if ported to *nix anyone would know to
move that to something more appropriate like:
  /home/data/abc_company/uv/acccounts/WAREHOUSE
In either case, the DBMS-level file system should abstract the MV
DBA from OS-level issues.  For example, we should be allowed to
create files like the following without OS-related issues:
  .TEMP
  OPEN-A/R
  CUSTMAST*DEPT
That said, the CREATE.FILE verb should also prevent the creation
of filenames that are commonly agreed as being "a bad idea", like
"CUSTOMER MASTER".

As always (like case sensitivity) this whole situation is just
another case of engineers who decide not to make changes because
they "speak Unix" and they expect the rest of the world to do so
as well.  The burden is not on them to make software work for the
target OS but on developers to have to know how another OS works
so that they understand why their own platform isn't working.
That's just lazy and backwards thinking.

Tony Gravagno
Nebula Research and Development
TG@ remove.pleaseNebula-RnD.com
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to