On Wed Aug 05/2009 @ 9:08:P +0200 asdasd, Miroslav Suchý wrote: > So little explanation: > This step means that we have schema definition which we can feed to > PostgreSQL. That mean definition of tables, procedures, indexes... > In fact - using tool chameleon we are able to create PosgresSQL schema > from Oracle schema anytime we want. > So DB population during spacewalk-setup should happened without error (I > mean this one single step, the script will likely die on something else > even before this one step). > And what is still remaining: > - ask in spacewalk-setup which backend you wanna use > - make sure that java, python and perl will load PosgreSQL driver when > you choose Pg. > - make sure that SQL queries in code is compatible with PosgreSQL (there > will be for sure with BLOBs handling). > - write Pg support for db utilites (like db-control) > - make performance tests with Pg. > - and probably something else I do not realize right now. > > > -- > Miroslav Suchy > Red Hat Satellite Engineering
The others mostly clarified but just to add some additional info these were also included in this merge: - ask in spacewalk-setup which backend you wanna use - make sure that java, python and perl will load PosgreSQL driver when you choose Pg. While things have gone backwards a little in the rush to cleanup the post-merge code, spacewalk-setup should come very close to completing against PostgreSQL. Cheers, Devan
pgp8EeVzqaK6y.pgp
Description: PGP signature
_______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
