[nycphp-talk] MySQL versioning system
Ophir Prusak
lists at prusak.com
Wed Apr 28 17:52:24 EDT 2004
This is almost exactly what I'm doing where I work.
We need to record all changes to data (what changed, when, and by who).
If using MySQL is not a must, then you should look into PostgreSQL.
You can use triggers (and rules) in PostgreSQL to automatically record
all the changes on table A into table B.
Ophir
Mark Withington wrote:
>I have a client who would like to store product development information
>within a MySQL table. The table will consist of multiple fields, each
>representing a product attribute (height, weight, color, etc.). The client
>would like to store each iteration (or version) of the product development
>information along with the ability to role back to prior versions if
>necessary.
>
>I'd like to ensure that I'm not reinventing the wheel on this. Anyone have
>any experience with such an effort? Is this kind of information stored in
>the MySQL logs? Any light shedding would be appreciated.
>
>Mark
>
>--------------------------
>Mark L. Withington
>PLMresearch
>"eBusiness for the Midsize Enterprise"
>PO Box 1354
>Plymouth, MA 02362
>o: 800-310-3992
>f: 508-746-4973
>v: 508-746-2383
>m: 508-801-0181
>http://www.PLMresearch.com
>Netscape/AOL/MSN IM: PLMresearch
>mwithington at plmresearch.com
>Public Key: http://www.PLMresearch.com/keys/MLW_public_key.asc
>Calendar: http://www.plmresearch.com/calendar.php
>_______________________________________________
>talk mailing list
>talk at lists.nyphp.org
>http://lists.nyphp.org/mailman/listinfo/talk
>
>
More information about the talk
mailing list