Klaus,
sorry for the delay, but I was restructuring the proposed design and I
wanted to have good news for you :-)
On 19.Nov.2001 -- 07:05 PM, Klaus Bertram wrote:
> I'm not at the team, but here idea for the descriptor file
No problem, perhaps I should have written "community" but that's twice
as many chars ;-)
> take the descriptor entry not from the table name when someone like me use large
>terms like
>
> <table name="hir_groups Left Join modul on(hir_groups.modules=modul.modules) Left
>Join sides on(modul.side=sides.name) Left Join styles on(modul.style=styles.name)">
As I understand the notion of the database actions they are no general
purpose DBMS layer but for a very restricted set of operations. In my
view they exclude joins. Thus I consider the above a misuse of the
actions. Anyway, you are right that if you're aware of the limitations
this "misuse" or should I say "extended application" :-) does make
sense in many cases. So, I have introduced an attribute @alias which
has precedance over @name for naming parameters. It is also available
for table-sets to refer to a @alias instead of @name. (The @name in
<table-set><table name="xyz"/></table-set> is checked against @name
and @alias in <table>).
Thanks for your input.
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
