[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNUe-dev] GCD samples
From: |
Reinhard Mueller |
Subject: |
Re: [GNUe-dev] GCD samples |
Date: |
Sat, 12 Jun 2004 15:02:18 +0200 |
Am Fre, den 11.06.2004 schrieb address@hidden um 22:57:
> Don't know if you are the right person, but when I've tried to run
> gnue-gcd2sql with every gcd file, html generation have failed with
> attached traceback.
We were unable to reproduce this traceback. However, we've found a
possible reason for it and fixed that. So maybe it will be fixed for you
with the final release.
> I've found also that gnue-gcd2sql --help reports --output option as
> 'to be added later' but it works.
Seems like you are right. We will also fix that before the release.
> I see codedict as a good idea for code reusing; it should be easy
> building a form that manages whatever code dictionary just with de
> code-type as parameter.
I generally don't see codedict as a very good concept. Usually, when a
table starts as a simple code/description pair, you end up needing some
more columns after time. And then, if you used codedict, you are lost.
> Instead, I wonder if it is usefull using UPDATE_Update properties in
> a generalized manner, because it says just about the *last* update.
I would hope that appserver at some point provides automatic
gnue_createdat, gnue_createdby, gnue_updatedat, and gnue_updatedby
columns in every table.
At a even later point, AppServer might provide a feature of "logging"
specific fields (for example item.sales_price). Usually you are not
interested about *all* updates on a table, but only on changes to
specific fields.
Thanks,
--
Reinhard Mueller
GNU Enterprise project
http://www.gnue.org
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
No army can stop an idea whose time has come.
-- Victor Hugo, 1802-1885
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil