On schema updater I thought I did a rename .... Oh well lemme delete the
one in java/scripts ...
Totally agree that spacewalk-schema-upgrade is the way to upgrade the
thing officially.. Well schema-updater is just for more fine grained
stuff.. Like Upgrade scripts starting from specific number and above..
Its useful only during devel phases as devs keep adding one table at a
time...
But sounds like the same can be achieved as Jan says by creating a
directory and symlinking exactly the files you want updated (me doesn't
think straighforwardly like that unfortunately :( ).
So every one use the official one the one under schema upgrade directory
as its more robust.. Jan is there documentation on the usage :)..
Partha
Jan Pazdziora wrote:
On Thu, Oct 30, 2008 at 11:22:06AM -0700, Mike McCune wrote:
For any development setups you will need to do the following:
1) Apply the following schema updates:
spacewalk/scripts:
./schema-updater --connect=<your db connect string>
--dir=/home/mmccune/devel/spacewalk/schema/spacewalk/upgrade/spacewalk-0.3-spacewalk-0.4/
--start=111
By the way, why do we have the exact same script in
spacewalk/java/scripts/schema-updater as well? Shouldn't we keep
one copy of that script, only, to avoid confusion?
I further wonder why not to use the spacewalk-schema-upgrade script.
I know that schema-updater was supposed to be more feature rich, but:
you should be able to achieve the start / end behaviour with
spacewalk-schema-upgrade by creating new directory with symlinks,
and more importantly: we expect our users to use
spacewalk-schema-upgrade to upgrade their Spacewalk Servers, and
expect our customers to use it to upgrade their Satellites. Any
testing or improvements we can give to spacewalk-schema-upgrade
will bring benefits to our users and customers.
Could we try to eat our own dog food?
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
