Re: OO BASIC or "B++"?

True - however these days i think you will find many an "Application"
is not just in databasic. Abstraction is deployed through many layers
via xml from the UI to the persistence layer. Many apps use databasic
to dish up data after applying certain specific business logic, to a
higher extracted layer which itself applies business logic and extracts
again to a higher layer etc.
Databasic is used to do what it is good at, other layers can then do
their bit. If you structure your app architecture correctly it becomes
highly maintainable. I know of some very un maintainable java software
out there (i used to work at a company with such code) so it is not a
case of "oo and abstraction " = "maintainable code" but good
architecture from the beginning using techniques like oo, and where
there is none to adapt.

rgds


PS - I like your line
"you can use code without direct reflection of domain-specific
abstractions, but then the mental burden of mapping between the
business domain and its reflection in code is much greater. "



Anthony Lauder wrote:

One of my big disappointments is that folks often talk about how
quickly they can develop an application in Pick - and I have seen this
to be true. At the same time, the lack of contemporary language and
database principles explicitly supported in Pick I worry deeply about
Pick applications lacking the malleability need to reflect ongoing
requirements changes. Typically, I see Pick-based applications falling
further and further behind the evolving requirements, until most of the
developers' time is spent on "fire fighting" and little on moving their
applications forward.

.

Relevant Pages

  • Re: Looking for a decent data access architecture to implement
    ... > application so that there is a clean separation between the data access ... > layer, the business layer and the GUI layer. ... > the actual database. ...
    (microsoft.public.dotnet.languages.csharp)
  • Looking for a decent data access architecture to implement
    ... application so that there is a clean separation between the data access ... layer, the business layer and the GUI layer. ... the actual database. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: "Business Objects" and the DAL
    ... layer talks to the layer next to it. ... business entity returned that up to the UI for binding to a grid. ... If a database table column names ... Each could be considered a "pattern", ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Size matters to some
    ... The underlying remote database connection ... physical layer is actually managing it all, the logical layer is forced to ... constraints as specified by developers. ... want to validate the information getting written. ...
    (comp.databases.pick)
  • Re: OO vs. RDB challenge
    ... > Layer 1. ... If you filter your data after you retrieve it, ... possible to redesign the database schema to enable SQL to do its job. ... A good RDBMS could integrate an external authentication server. ...
    (comp.object)