Freeside not SQL compliant?

[Stephen Amadei]

Hello guys.  

First I wanted to tell Ivan and co, just how impressed I have been with
the Freeside product.  I really like it and feel I'll like it alot more
once I have it running.

Next, I'd like to give everyone a good laugh by explaining how I am
attempting to use Freeside... (Iceskating uphill in Hell is close)

... I am a DB2 programmer, usually in a OS/2 environment, so when I saw
Freeside would work with any DBI interface, I was thrilled to find a DB2
DBI.  I have since compiled my own fresh version of Perl, added the
necessary Perl mods, set up DB2 and Lotus Go Webserver to run Freeside.
The Freeside needed minor changes to accommodate OS/2... it didn't like
the file's with ':' in them, so I changed them to '.'s and I needed to 
change a couple paths from '/usr/whatever/freeside' to 'd:/freeside'.
These changes should also allow Freeside to run under that lousy OS from 
Redmond.

Basically, everything looks ready to go, but while running fs-setup,
(well, fs-setup.cmd for me) the tables don't what to be created...
alot of the labels (column names, table names, index names) are over the
SQL limit of 18 characters and one includes the '_' character as the first
character ( _date)... a SQL no-no.

I was wondering, since most RDBMs are somewhat SQL compliant, if there
are plans for Freeside to be more SQL friendly, or if there is a newer
SQL standard that MySQL and PostGres are using...

In any case, I'm just about to undertake a massive label-shortening
campaign on my copy... ;-)

					----Steve
Stephen Amadei
Director of MIS
Dandy Connections, Inc.
Atlantic City, NJ