mySQL 5.x database server

[jubie]

---

pag postgresql nalang mo, mas kusog pasa mysql tested na nako with million of records.

[BadDudes]

@ gloryhunter .. nice info got to check it out ... pero bai how about performance no effect ba?

@ jubie .. hmmm no ones comparing

[gloryhunter]

baddudes,

about the peformance, it's not an issue. Yes, it's an additional layer but it's easy to cache the objects you have create and retrieved. It's easier to scale up as well by clustering the objects.

[simoncpu]

R/ODBMS is inherently slow, what with the overhead in the parsing and optimizing of the queries. They may be suitable for applications that don't need to do be very efficient (i.e., web apps or programs that are interpreted by a byte-code interpreter... lolz), but if you are concerned with performance and that you can predict how you need to use your data in advance, you might want to explore Berkley DB, a "transactional storage engine for un-typed data in basic key/value data structures", and feel the power. :mrgreen:

[ simon.cpu ]

[BadDudes]

@gloryhunter .. as of the moment ..were using both front-end and back-end dev tools on single vendor .. so as of now we dont usually need to have an OR mapper but then again .. but we are expecting to have mixed culture of developers and deployments .. so most probably we'll try it

[olybrius_e]

Better use postgre complete na jud kaau cya with triggers and views. ang My5 kai views raman. ang much faster ang postgre.