a*****i
发帖数: 4391 | 1 bah , it doesnt even support transaction! | ug
发帖数: 1643 | 2
Really!?
If that is the case, it can not be called DBMS.
【在 a*****i 的大作中提到】
: bah , it doesnt even support transaction!
| b****e
发帖数: 1275 | 3 it doesn't support cursors either .. does it support
stored procedures? i don't know
【在 a*****i 的大作中提到】
: bah , it doesnt even support transaction!
| p**v
发帖数: 7 | 4
Nah..:) And it doesnt support complex sub-query either...:)) But its pretty good to used
as a read-intensive, cache like database. I am still using Oracle to do complex
data processing tho, but I can avoid overcharge by oracle by using mysql, thats
why I like this cute thing..:))
Besides, even with buffering catche, I still dout Oracle' speed, that only apply
to similiar query, and limited by your buffer size too..:)
【在 b****e 的大作中提到】
: it doesn't support cursors either .. does it support
: stored procedures? i don't know
| t****e
发帖数: 48 | 5 i will say somethings good about mysql.
1. thought it does not support transaction, to be presice,
it does not support roll back, it support atomic operation.
for some type of application, it is good enough. in the future
version, mysql will support berkeley DBT which is transaction
safe.
2. it support stored procedure and trigger. but it is said explicitly
trigger can greatly slow down the execution speed.
【在 p**v 的大作中提到】
:
: Nah..:) And it doesnt support complex sub-query either...:)) But its pretty good to used
: as a read-intensive, cache like database. I am still using Oracle to do complex
: data processing tho, but I can avoid overcharge by oracle by using mysql, thats
: why I like this cute thing..:))
: Besides, even with buffering catche, I still dout Oracle' speed, that only apply
: to similiar query, and limited by your buffer size too..:)
|
|
