If your client has the bucks and you need the speed, why not use a MySQL
cluster which has row locks and transactions?
Mike
At 11:39 AM 5/15/2007, you wrote:
If there are no holes in the data structure storing the MyISAM data,
this concurrency is possible but as soon as any real-world maintena
If there are no holes in the data structure storing the MyISAM data,
this concurrency is possible but as soon as any real-world maintenance
kicks in, those holes will exists and the rules kick in:
on MyISAM you may have 1 writer OR many readers.
a write operation will wait for ongoing read ope
In the last episode (May 15), Dan Buettner said:
> Hi Edoardo -
>
> I think you've been misinformed; MyISAM tables do not support
> simultaneous read and write operations. MyISAM is a multiple
> reader/single writer, table locking design. You may want to switch
> to InnoDB tables for that f
Hi Edoardo -
I think you've been misinformed; MyISAM tables do not support simultaneous
read and write operations. MyISAM is a multiple reader/single writer, table
locking design. You may want to switch to InnoDB tables for that
functionality.
http://dev.mysql.com/doc/refman/5.0/en/locking-iss
Hi Guys,
we have a MySQL server acting as a backend for a VoIP provider.
We're using this MySQL server to collect CDRs and to extract some easy
reports from them (including web access to CDRs for customers)
CDRs are inserted directly from Asterisk switches when a call ends.
We're using
