Michael Stahnke wrote:
Perhaps you could explain this a little more. When I read that the
Postgres Merge happend, I assumed that meant Postgres functionality.
Also, in reading Cliff's notes for Spacewalk 0.6, it looked like
Postgres support was in there. Am I just mis-reading things, or is
there more to it? I am sure it's a very significant effort for the
whole process, I just want to be sure I understand where it's at.
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
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
