In article <741js4$mvs$1_at_eros.clara.net>, Paul Smith
<paul.smith_at_clara.net> writes
>I have hit a brick wall as far as applying any reasonable version control to
>a Designer application.
>My main VM tool is PVCS, but this offers no hope of controlling repository
>items unless I export them after every change.
>This isn't very practical.
>
>I can't believe that this isn't a fairly common requirement, so has anyone
>found a solution?
>
>Any help appreciated.
>Regards, Paul.
>
>
you could use the internal version of the tool but basically it just
makes a copy of everything in or shared into the application and you'll
soon run out of database space.
In the past 5+ years with oracle I've found very few occasions when you
want to version the whole repository - usually what we have done is
generate the ddl and put that under version control along with the
forms/reports etc.
You really need to decide what you are using version control to achieve.
The next version (whatever they decide to call it and whenever it's
available (and I don't mean 2.1.2) is supposed to include proper version
control but I'm not holding my breath! :-)
--
Diane
Received on Wed Dec 02 1998 - 00:00:00 CST
