MESSAGE
| DATE | 2002-08-19 |
| FROM | Justin Clift
|
| SUBJECT | Subject: [hangout] Re: [Marketing] OOo...the Vision thing
|
Hi Ruben,
Ruben I Safir wrote:
>
> You need to rethink it.
>
> MySQL and Postgres is the only real acceptable answers
Heh Heh Heh
Like, you'd recommend a database to people which is extremely optimised
for read-only situations, has a reputation for corrupting itself, and
doesn't even support most stuff which people will need if their
application starts to become significant in their enterprise?
MySQL is a very good *website* database. It's *not* an *application*
database. There *is* a difference.
> I would not install any other database servers on any system.
>
> MYSQL is the easiest choice to make and you should find a way
> to make this happen.
It's only an *easy* choice if you're really familiar with just it and
not the other possibilities.
People that are familiar with MySQL *and* other databases might not
recommend it so fast. (i.e. NuSphere just for starters)
> I would be happy to be an intermediary between Monty and You.
Of course. Monty would *love* you to get MySQL officially into
OpenOffice, and thereby secure a *huge* automatic userbase for MySQL...
pity that it can't actually do what people will need from here and into
the future, let along scale up to department sized loads, etc. And if
you want to then migrate to a more powerful database server, such as
Oracle, DB2, Sybase, expect them to be massively inefficient until you
re-write your application. They do things efficiently in 1 SQL query
which MySQL requires 4+ for, because it doesn't know how to do SQL very
well.
> Also, this idea that every machine has to have the local database server is
> an error. As for resources, if it's on a W2K machine (it's almost funny talking
> about resource issues with Open Office being HOG - oink Oink), run it in single
> mode.
>
> Part of NYLXS's evaluation of Open Office is specifically it's ability to
> integrate with MYSQL easily.
Good. It's called ODBC, JDBC, etc, same as the rest of us without
native drivers at present have.
> Because of the install base alone, this is a facts on the ground decision.
The majority of people who need a database on a website don't need
transactions, subselects, an system optimised for scalability, etc.
They need a database which "does the job" for their website.
A *business* person or a *home user*, needs a database which is capable
of all kind of things.
MySQL is *not* going to be packaged along with OOo. There are enough
*experienced* DBA's around to be able to explain to you in *depth* why
if you really, really, really, really want, but the people here have
been through this before.
Regards and best wishes,
Justin Clift
> Ruben
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
____________________________
New Yorker Free Software Users Scene
Fair Use -
because it's either fair use or useless....
|
|
