On Tue, 4 Aug 2009, Jesus M. Rodriguez 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.
To my knowledge the postgres merge was a very small step on the path to
supporting PostgreSQL. The schema was reorganized and standardized to
work with a new sql build tool called chameleon. The purpose of this is
to allow us to maintain both PostgreSQL and Oracle schema. IIRC, the
PostgreSQL work is not done yet and quite a bit a ways away.
So in short, Spacewalk 0.6 will *NOT* support PostgreSQL :)
Of course, what this *does* mean is that work for this migration can now
start in earnest -- and that anyone can participate. The more people are
willing to help, the shorter a road it will be.
Seems like the critical path, at this point, is to identify every single
place where the code breaks in Postgres and rewrite the query
appropriately. It won't be easy, and it won't happen overnight, but it
does lend itself to spreading the work to many hands.
Which is what I'm thinking about now: how do we do that correctly?
--g
--
Computer Science professors should be teaching open source.
Help make it happen. Visit http://teachingopensource.org.
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
