On Sun, Dec 17, 2000 at 09:43:48PM -0600, Christopher Browne wrote:
>
> And the issue is _quite_ to the point, irrespective of anything
> having to do with MySQL.
>
> The examination of DB schema has thus far concentrated on what the
> field types need to be; that is important enough, but only goes half
> way towards describing the data.
>
> The _next_ thing that needs to be done is to outline the relationships
> between table entries.
I've done a preliminary entity relationship diagram, or the ASCII
equivalent, anyway :-) in the design doc. I actually made a lot of
changes today.
> Assuming "standard" SQL, that might be outlined in the form of a number
> of foreign key relationships.
>
> Supposing the SQL is "dumbed down" to the lowest common denominator
> form supported by MySQL, that means that we need to establish what the
> relationships are that the _engine_ will have to manage.
>
> What may ultimately prove necessary is to build something like CORBA
> IDL that outlines the operations supported by the engine.
Yes, exactly.
--
Dr. David C. Merrill http://www.lupercalia.net
Linux Documentation Project [EMAIL PROTECTED]
Collection Editor & Coordinator http://www.linuxdoc.org
Finger me for my public key
Under the full moon light we dance
Spirits dance, we dance
Joining hands, we dance
Joining souls rejoice!
-- Karen Beth
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
