Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!dciem!nrcaer!cognos!erics
From: erics@cognos.uucp (Eric Schurr)
Newsgroups: comp.databases
Subject: Re: Database Machines
Message-ID: <1026@sirius.UUCP>
Date: Thu, 2-Jul-87 08:33:20 EDT
Article-I.D.: sirius.1026
Posted: Thu Jul  2 08:33:20 1987
Date-Received: Sat, 4-Jul-87 11:30:02 EDT
References: <2861@blia.BLI.COM> <2918@zen.berkeley.edu> <131@hippo.UUCP>
Reply-To: erics@cognos.UUCP (Eric Schurr)
Organization: Cognos Inc., Ottawa, Canada
Lines: 21

>	This does, of course, have the problem of having to change the
>application(s) if you decide to move the data partitioning around. I 
>like the Sybase approach to this - namely the transactions are stored
>in the database itself, rather than in the applications. While you still
>have to change the transactions if you change the schema, at least they
>are all in one place, and the applications themselves do not have
>to be rebuilt.
>

This statment intrigues me.  I don't know anything about SyBase--do
they allow you to model/define *transactions*?  Is this simply referring
to table (file/record) definintions or to the much broader--and more
complicated--notion of a transaction?  What mechanism do they use to
define and report this?


-- 

Eric Schurr           3755 Riverside Dr.
Cognos Incorporated   Ottawa, Ontario       decvax!utzoo!dciem!
(613) 738-1440        CANADA  K1G 3N3       nrcaer!cognos!erics