On Wednesday 09 October 2002 9:41 am, Ariz Jacinto wrote: > i've used both MySQL and PostgreSQL but the obvious choice > for your problem would be PostgreSQL. besides, i'm using PostgreSQL > on the same application you've mentioned.
Just curious, are you the guys who do the application backend software management for digi fema digital weighing/printing scales? Our shopping mall bought these digital weighing scales from a local distributor, Therismus industries. Therismus showed us the backend management software and we were impressed. Featureful and extensively documented, plus it's easy-to-use for the wet-market staff. Does the backend use PostgreSQL? > One of the features that MySQL lack is the "ROLLBACK" Yup. Rollback is one feature that I like. The ability to program what and when to implement rollback is nice. When the counter conks out for no apparent reason at all, it's nice to restart the application and do automatic rollback. > Try using unixODBC (http://www.unixodbc.org) to your application > coz it works on most popular databases and so that you dont have > to re-code your software again whenever you migrate to other > databases. I'd love to switch the GUI Win98 clients to Linux GUI toolkits such as Qt and Gtk but these toolkits are still rough and they're not easy to integrate in a RAD environment. Perhaps someday. At the moment, I can replace the NT4.0 database server with a Linux database server, which is really neat. Thanks. -- mikol "There is no concept more closer to intellectual emancipation than free software. Freedom to responsibly code and share in its most free and pure form." -- Floyd Robinson, September 24, 2002 _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
