From: Danie B. <su...@na...> - 2004-02-24 06:54:04
|
On Tue, 2004-02-24 at 14:22, Phil Daintree wrote: --Snip-- > This is effectively what we have with the script includes/ConnectDB.inc - > this script contains all DB specific functions. It is simply (?) a matter of > making a new ConnectDB.inc for Postgres, MS SQL Server, Oracle, DB2, > Firebird etc. I will see what I can do about conversion to Postgres, OK. --Snip-- > If Perl is the client program there is only ever one user of a POS > terminal.... its just there are Perl POS systems about - rather than > complete re-invention of the wheel? The reason I am pro python is simply that it can scale fairly well, I do not mean network/user like. And of cause it is a language I know. However I know about 10, learning number 11 should not present to much of a problem. Send me a Perl POS link and I will see what it looks like and if I can understand it. I still in the process of downloading Java POS ( previous link) to evaluate as well. --Snip-- > The EDI system could send orders and invoices true. We could manage > something much simpler for internal transfers of orders though. To keep > location stock and all aspects of the business updated is much more serious > though. Would need a very clear spec on which aspects of the business > transactions are to be reflected on each system. --Snip-- It seems to me, that simply packaging all SQL relate posts to the database in some form, would allow for these changes, I will investigate this. Probably not SQL as it rely on Table ID's which is inappropriate. --Snip-- P.S. Leap of faiths for most of my clients is not a problem, installing one today. Installing 1.7. And the next 2 weeks from now. Kind Regards Danie Brink su...@na... |