On Wed, Dec 19, 2001 at 02:58:18PM -0800, Karsten M. Self wrote:
>
> The usual criticism of MySQL is that it is not ACID.
But it is. Use InnoDB tables.
> For quick, temporary, storage, MySQL may be a fit. For robust
> database use, it's probably not advisable.
We have hundreds of queries per
martin f krafft ha escrito:
>
> hi,
> *PLEASE DON'T MAKE THIS INTO A FLAME WAR*
> if you are taking anything personal, please don't reply...
>
> [...]
>
> could you shine some light on these and other aspects, please?
http://openacs.org/philosophy/why-not-mysql.html has an excellent
discussi
> hi,
> *PLEASE DON'T MAKE THIS INTO A FLAME WAR*
> if you are taking anything personal, please don't reply...
>
> i have always used postgresql for everything. i don't really know
> why, but i know that it's a pretty scalable, high-performance
> database
> server that is secure and powerful.
i h
> This would be true if it was true, but it isn't. MySQL is really unsuited
> to multiple readers, unless the reads are trivial select-one-row-by-id
> jobs.
Flame bait. MySQL has been great for us, with scads of multiple
readers with complex queries. Your mileage may differ, hence try them
both
On Wednesday 19 December 2001 12:18 pm, martin f krafft wrote:
> hi,
> *PLEASE DON'T MAKE THIS INTO A FLAME WAR*
> if you are taking anything personal, please don't reply...
I'm not even going to touch the mysql vs postgresql debate, but I just now
received Martin's original post after I had alre
on Wed, Dec 19, 2001 at 07:18:20PM +0100, martin f krafft ([EMAIL PROTECTED])
wrote:
> hi,
> *PLEASE DON'T MAKE THIS INTO A FLAME WAR*
> if you are taking anything personal, please don't reply...
>
> i have always used postgresql for everything. i don't really know why,
> but i know that it's a p
also sprach Jeffrey W. Baker <[EMAIL PROTECTED]> [2001.12.19.1936 +0100]:
> The differences are basically these: postgres has better concurrency, so
> selects never block selects, updates block selects on a per-record basis.
> In mysql, updates, inserts, and selects all block each other except in t
On 19 Dec 2001, Paul Smith wrote:
> %% martin f krafft <[EMAIL PROTECTED]> writes:
>
> mfk> a client of one of my servers has recently requested mysql. i
> mfk> need postgres, so i'd install mysql in parallel, but i first
> mfk> would like to know about the negative aspects. from what i
>
%% Lev Lvovsky <[EMAIL PROTECTED]> writes:
ll> On Wed, 19 Dec 2001, Jeffrey W. Baker wrote:
>> Oh, and don't go anywhere near mysql 4.
ll> care to be more specific RE the warning?
MySQL 4 is beta. 'Nuff said.
--
--
%% martin f krafft <[EMAIL PROTECTED]> writes:
mfk> a client of one of my servers has recently requested mysql. i
mfk> need postgres, so i'd install mysql in parallel, but i first
mfk> would like to know about the negative aspects. from what i
mfk> remember, mysql isn't a true database, an
On Wed, 19 Dec 2001, Jeffrey W. Baker wrote:
> Oh, and don't go anywhere near mysql 4.
thanks for the info up top...I'm actually in the process of choosing b/w
these two right now...
care to be more specific RE the warning?
-lev
--
personal site :: www.sonous.com
rave site :: raves.sono
On Wed, Dec 19, 2001 at 12:24:20PM -0600, [EMAIL PROTECTED] wrote (0.07):
> I have always used mysql and have never used postgresql, so I'm
> interested in this too. But, What do you mean about MySql not being a
> true Database?
MySQL didn't have transaction or rollback support, which means that
I have always used mysql and have never used postgresql, so I'm interested in
this too. But, What do you mean about MySql not being a true Database?
Wayne
martin f krafft <[EMAIL PROTECTED]> wrote ..
> hi,
> *PLEASE DON'T MAKE THIS INTO A FLAME WAR*
> if you are taking anything personal, pleas
On Wed, 19 Dec 2001, martin f krafft wrote:
> hi,
> *PLEASE DON'T MAKE THIS INTO A FLAME WAR*
> if you are taking anything personal, please don't reply...
>
> i have always used postgresql for everything. i don't really know why,
> but i know that it's a pretty scalable, high-performance databas
hi,
*PLEASE DON'T MAKE THIS INTO A FLAME WAR*
if you are taking anything personal, please don't reply...
i have always used postgresql for everything. i don't really know why,
but i know that it's a pretty scalable, high-performance database
server that is secure and powerful.
a client of one of
15 matches
Mail list logo
