Thierry,
Is there a way to do this through meta-data style definitions? In
the past, when I've wanted to do this, I've found it easiest to build
generic style tables (like fieldName, value) and use additional pre-
defined tables to define the customer's data.
If they don't need to query the database directly or use a report
writer (and meta-data style tables would require more joins, etc),
this might be a nice solution. What you're asking to do is possible,
but certainly more work...
Ken
On Jun 9, 2007, at 5:46 PM, Thierry Kramis wrote:
Hi
I need to give a customer the possibility to create it's database
within our
existing Webobjects application. So the base application stands
with it's
first eomodel. The customer should now be able to login and then
define the
tables and the attributes dynamically in a second separate eomodel
himself.
All our existing app would do is to create the eomodel that he
defined and
then write this to the database so that the customer can work with
that
second database and adapt it to his needs.
Is there any way to do this and could anyone help on explaining how
to do
this with Webobjects?
Thanks.
tk
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/kenlists%
40anderhome.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
