Re: No API mention, any suggestion that would 'conform' to a coding standar

[Dieter S. <dsi...@sq...>]

The id is unique. Table links are in the form of {table}_id, meaning if
you link table xyz to table customer one of the fields in table xyz is
called customer_id. This way you can almost always tell which tables are
linked by just looking at the schema.

If there are changes to the tables or new tables are being added, the
changes are in the upgrade scripts.

To avoid nameing conflicts reference your table with a variable. This
way you can rename the table in question and make one small change to
the backend.


Dieter Simader    http://www.sql-ledger.org   (780) 472-8161
DWS Systems Inc.     Accounting Software       Fax: 478-5281
=========== On a clear disk you can seek forever ===========

On Mon, 25 Feb 2002 mtr...@du... wrote:

> d for SQL-Ledger (and point to implementation talk on another list)
> From: MR
> To: <sql...@li...>
> X-Mailer: Sendmail by hand
> 
> I want to add some additional account info, like bill rate, and how the data 
> flow the the client is handled.
> The API section of the web site is a bit light, but is there any convention
> declared yet for table names that won't get stepped on in upgrades?   
> Even though id or name are not set to unique, I'm going to go with the 
> idea that they ARE unique, and use the ID to tie into the second table.  
> (unless I missed something.) 
>  
> The accounting talk over on gn...@gn... is bringing up 'standards documents' 
> for the design/implementation of accounting systems.   Links to documents
> are all over the thread, so if you are NOT on the gnue list, and find 
> accounting standards exciting, then go polk around on www.gnue.org 
> and get the last 2 weeks of mail list archives.
>  
> A couple of links from the thread: 
> http://www.xbrl.org/gl/gl.htm
> >http://lists.ebtwg.org/archives/ebtwg-ccs/200111/msg00084.html
> >http://lists.ebtwg.org/archives/ebtwg-ccs/200111/msg00092.html
> >http://www.diffuse.org/0201-ec.html
>