SCO Survey concerning MySQL

[Fairlight]

Is it just me, or did Walter Vaughan say:
> Woops! Me wrong. You right.

There's like a first.  I'll mark my calendar!  :)

> http://www.caldera.com/products/mysql/scamp.html

The ironic thing about this is that SCO doesn't keep their versions
current.  ftp://ftp.sco.com/pub/openserver5/opensrc/  Look at their apache
version.  1.3.33.  Now look at http://www.apache.org/dist/httpd/CHANGES_1.3
and notice the big honkin' SECURITY fix in 1.3.34.  SCO doesn't provide
1.3.34.  The .txt file in the directory for their release makes no notes
about any "undeclared" changes that would make it as secure as .34 as the
linux vendors often do with rpm versioning and --changelog entries.  For my
money, I don't trust it.

SCO has -always- been behind on keeping releases up to date in regards
to third party software.  And I'm talking since the first Mosaic through
Netscape 3.2.  They were a version behind on many things.  That is NOT good
enough when vulnerabilities are discovered.  Compiling it one's self is a
complete PITA for some packages--especially with only gcc.  But you -need-
gcc because their stock cc isn't ANSI compliant.

Let's put it this way:  I'd put a SCAMP solution up...never.  For my money,
even if I had to -buy- a commercial linux server at SCO prices, LAMP is
peace of mind.

> http://www.caldera.com/products/meinc/

Thanks.

> > As for the "multivalued" part, what do you mean, exactly?  I'm not
> > grasping your whole meaning.
>
> A least three of those databases are multi-valued or you may know them as
> PICK like systems.
>
> http://www.pickwiki.com/cgi-bin/wiki.pl?MultiValuedDatabases

Apparently my lack of -formal- DB training is showing.  I understand about
1/3 of what they're trying to convey.  Okay, let me ask this--how are MV
databases "bad"?

mark->