On Fri, Sep 07, 2012 at 04:10:13PM +0200, Jan Pazdziora wrote: > On Fri, Sep 07, 2012 at 03:54:25PM +0200, Bo Maryniuk wrote: > > > > The /etc/rhn/rhn.conf has nothing to do with *Oracle* database > > at all. > Right, besides providing database type and connect information, which > for Oracle backend turns out to be ... Oracle connection > specification. :-P
One more time: /etc/rhn/rhn.conf has nothing to do with *Oracle* vendor. It has everything to do with providing a *generic* information for database connectivity, which can be Oracle or PostgreSQL (as of today). The problem is that built tools around the Spacewalk now needs to be also changed to specifically parse the URI and also determine in "if/else" fashion is it URI or just a name, if some other fields left empty etc. Users, that are using PostgreSQL version now have to worry about Oracle-specific hardcoded ad-hocs and the documentation now needs to contain trash like "If you use Oracle, then.... and if PostgreSQL, then.....". Instead of just work as before. So the question still remains: what was the REASON to change what is working rock-solid for years? And another sub-question: why it is not called "db_uri" (because it *is* URI)? -- Bo Maryniuk SUSE LINUX Products GmbH, HRB 16746 (AG Nürnberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer There are 10 types of people in the world: those who understand binary, and those who don't. _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
