Re: sql-ledger and postgresql: HOWTO?

From: Helmut Wollmersdorfer (helmut.wollmersdorfer_at_gmx.at)
Date: 08/05/04

  • Next message: Raymond Johnson: "RE: Debian Install problem" 
    To: debian-user@lists.debian.org
Date: Thu, 05 Aug 2004 13:53:56 +0200

    Oliver Elphick schrieb:

    > I'm not all that keen on web interfaces; as far as I can see, from my
    > limited and reluctant experience of writing them, the programming
    > languages are poor and debugging is a nightmare.

    That's true. But a web interface has the advantage, that the ledger can
    be used from anywhere. Even restricted user accounts can be given to
    business partners. So they can see their own account. For a small
    association, where I am the financial administrator, our bookkeeper
    wrote such an small ledger in Apache+PHP+Postgres. Each member can look
    into his own account and into the consolidated profit+loss, even can
    change some of the own data like address, email etc. And he can see the
    original document/check of his payment - just one click away. It's
    paperless.

    The disadvantage is, that strokes from the keyboard cannot be supported
    easily by an web interface. The same is true for some context dependent
    logic and data.

    You need both: a webinterface and a GUI-client with local logic.

    > I was thinking on the
    > lines of glade + Python or Eiffel. However the underlying database
    > structure should be the same, and I would insist on putting all the
    > consistency rules into the database (triggers, foreign keys, etc.) so
    > you could possibly have two different interfaces to the same database.

    Interface layers?
    You can see a database as a storage interface. Users like to use their
    own favorite database system like Postgres, MySQL or Oracle.
    Exchangebility is a good design principle.

    Helmut Wollmersdorfer 

    -- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Raymond Johnson: "RE: Debian Install problem"

    Relevant Pages

    • Verifying Whether Account Is in Use Before Running Script
      ... I've scripted an account management section for the database ... database's interface rather than having him work with FM's interface ... It seems like the best thing would be to have the script check whether ...
      (comp.databases.filemaker)
    • Re: Beginning C# Q
      ... starting out with a network app0lication, you have an awful lot to swallow. ... Designing your database is therefore, not quite the first step, particularly ... Groups table, which defines which Groups users belong to, and a Permissions ... That is why an Interface is called an Interface. ...
      (microsoft.public.dotnet.framework)
    • Re: Transaction Oriented Architecture (TOA)
      ... If one builds the application around the database view, ... The problem solution should not have to know about mechanisms like SQL query construction, optimizations like anticipatory caches, or encoding/decoding of dataset formats. ... Note that the CRUD/USER environments already provide exactly that encapsulation by providing a Data Layer that is isolated from the rest of the application through an interface. ... TOA/TOP proposes the database and its application domain stored procedures are the only persistence mechanism necessary, and that the benefits of a focused, single, data-permeable gateway between application and database far exceed the benefits of O/R mappings--regardless of abstraction--and that its lightweight appearance shouldn't be dismissed as missing heavyweight kick. ...
      (comp.object)
    • Re: Transaction Oriented Architecture (TOA)
      ... I don't think the issue is ignoring the database; it is recognizing that the database is a different subject matter applying different business rules than the problem solution. ... There is nothing to prevent abstracting the database subject matter in a classic OO manner with objects like Schema, Table, Tuple, and Query. ... I'm of the opinion that the more obvious the database (or at least its interface) is the more easily maintainable an application becomes. ... I've nothing against creating frameworks and patterns to facilitate those programming activities, but prefer the concept of a problem domain transaction to language-specific expressions mapping 1:1 with anything physically present in the database. ...
      (comp.object)
    • Re: OOP style
      ... Component classes have all their main logic in a Custom base class ... database access unit if they didn't already start with a full DB layer; ... My latest application started with an extensively designed object model ... Typing in the implementation of the database interface is ...
      (comp.lang.pascal.delphi.misc)