Le 07-06-10 à 04:18, Thierry Kramis a écrit :
this might be a nice solution. What you're asking to do is possible,
but certainly more work...
How would I realize this then?
Consider that all the comments bellow have not been tried by me, they
are pure _speculation_ based on what I know ..
Hi, Thierry,
You might have noticed some hesitance in the replies you've gotten.
That's because you're describing a very general, but particularly
difficult problem, the value of whose solution might never approach
the magnitude of the effort you'll put in to solve it if it isn't
bounded
Thierry,
I don't really have much to contribute to the discussion, except that
I would not try to use WO in this way. I think it will only bring you
tears, and many of them. If I were you I would try to find some other
persistence framework, one that was made to do with what you are
thin
Hi Thierry,
maybe the GVCVirtualTabes framework can help with that problem. It is
included in the GVC Frameworks:
http://www.gvcsitemaker.com/marketing/download
Examples of it's usage are here
http://www.gvcsitemaker.com/marketing/benefits/__data_tables
and here
http://sitemaker.umich.edu
Don't know if this is the way to go because I wanted to preserve my database
independency...
Am 10.6.2007 3:37 Uhr schrieb "jerry porter" unter <[EMAIL PROTECTED]>:
> Check this url out.
> http://www.stepwise.com/Articles/2005/DBChanges/index.html
>
> I use this exclusively in my apps.
>
> --
Am 9.6.2007 23:53 Uhr schrieb "Ken Anderson" unter <[EMAIL PROTECTED]>:
> 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 pr
Check this url out.
http://www.stepwise.com/Articles/2005/DBChanges/index.html
I use this exclusively in my apps.
--- Ken Anderson <[EMAIL PROTECTED]> wrote:
> 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 i
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 t
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 h
