Antonio Gallardo wrote:
Don't agree. It is posible to do with them a lot of work. They are stable and not buggy. The reasons to I don't recommend them is because the maintenance of the system is more complicated. That is all! With O/R mapping it is more easy the later maintenance work.
For the records, in mid-2003, we developed a payroll system using Modular DB Actions.
The system was developed for a company that sells payroll services to other companies or corporations. We need to keep track on the system about all the operations of this company.
Under some circunstances the system needs to mix some companies. In some cases there is people with a high rotation (some times a person is hired and fired more than 5 times monthly) and other cool things. The system allow a lot of flexibility for our Nicaraguan laws. And I am talking about our laws, because for sure, were done without a computer in mind.
And I can tell that Modular DB actions pretty good managed the system. In fact we just found 1 or 2 cases where was imposible to use Modular or Original DB Actions. In the system we complemented with stored procedures and java some business logic. The database was of course PostgreSQL. Some statistics: 44 tables, 197 stored procedures, 22 sequences and 6 views.
This is why I think we cannot tell that they are buggy and unstable. In fact we started to develop the system with Cocoon 2.1.0 and it was worked in all versions even today in the lastest 2.1.7-dev on the current SVN. Without changing a line of code while migrating between cocoon versions!
i disagree violently :)
we are currently refactoring an application that is infested with them, and we found several bugs. let me see about releasing those fixes.
-- Gregor J. Rothfuss COO, Wyona Content Management Solutions http://wyona.com Apache Lenya http://lenya.apache.org [EMAIL PROTECTED] [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
