Re: Transaction Oriented Architecture (TOA)

Implementing our system with a TOA/TOP design has afforded us unusual
responsiveness to fixes and enhancements--many able to wind their way
through development, QA, and into production within hours of the
request--with minimal changes to applications. The fewer changes we
make the faster and more confidently we can move to production.

I see no reason why a flexible RDBMS cannot do the same. Switch to
PostGre, the most powerful open-source RDBMS, and add features that it
does not have that you need.

Further, whatever wrapping you suggest for SQL, procedures can do the
same. OOP is not required to wrap SQL. I do function-based wrapping all
the time for commonly-used SQL activities. Thus the "should wrap SQL"
and "OOP wraps better" issues/claims are generally different issues.
I'll believe OOP wraps better than procedural only when I see
side-by-side comparisions of typical, common, and representative
scenarios.

I'm a little confused about what aspect of the OP's posted article you
disagree with. The article mentions OO design principles, but does not
appear to advocate wrapping SQL in OO constructs, or even using any OO
constructs at all. What the article /does/ suggest is the use of a set
of stored procedures to act as an API for application programmers
writing code against the database. With a well-defined API in place,
you can change the applications and the database independently of one
another as long as the API stays the same.

That sounds like a solid approach to me by itself. The article does go
farther than that of course, leveraging the stored procedures to
implement detailed auditing within the database. But I don't understand
your objection to keeping an audit history in database tables either.
If you need an audit trail, and all access to the DB is through the
stored procedure API, adding audit functionality would be rather easy
to do. Are you suggesting that it would be /less/ work to compile a
custom version of Postgres?

- Matt McGill

.

Relevant Pages

  • Re: Serious errors with Create view command
    ... the database is opened? ... There's no database on earth that behaves that way! ... What on EARTH does the option of 'Edit Stored procedures' do? ... I can't paste it INTO the view designer sql view ...
    (microsoft.public.fox.helpwanted)
  • Re: Get all stored procedures
    ... For SQLSERVER, we can use the following SQL statement to query the SP ... objects of a certain database: ... Microsoft Online Support ... | Thread-Topic: Get all stored procedures ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Cannot Open SQL Server Table in Access.ADP File.
    ... I dont think that SQL Server will take 'veiw dependencies' into effect; ... Generate Script Wizard did not work on my original database, ... After fixing some of my tables and a few stored procedures and views, ...
    (microsoft.public.access.adp.sqlserver)
  • Re: converting sql db to plaintext db
    ... What is the "PHP-TextDB API"? ... You would have none of the advantages a SQL database would ... You could host your website on a webserver that provides database ... With the "Txt-Db-API" you can access normal Text Files like a SQL Database. ...
    (comp.lang.php)
  • Re: Serious errors with Create view command
    ... However the REASON I thought it should work on 'opening' the database was ... Why should I have asssumed that an SQL statement which works ... Stored procedures are nothing more than procedures that are stored in the ... There's no database on earth that behaves that way! ...
    (microsoft.public.fox.helpwanted)