On May 25, 2006, at 7:16 PM, Jon Jensen wrote:
Yeah, sorry, I meant start of statement vs. wallclock time. Both
MySQL as of 5.0.13 and PostgreSQL since forever (AFAIK) give you a
way to get the wallclock time, but their now() pegs the time at a
different starting point.
Yep.
pg's now() @begin is nifty, because the timestamp essentially becomes
a transaction id. i don't think that its unique enough to be an
actual transaction id, but it is super useful for debugging.
after some particularly bad experiences with the DB itself , i hope
to never use mysql again - but i think emulating that behavior would
be a real plus for rosedb mysql users.
| - - - - - - - - - - - - - - - - - - - -
| RoadSound.com / Indie-Rock.net
| Collaborative Online Management And Syndication Tools
| - - - - - - - - - - - - - - - - - - - -
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object
