Bo Maryniuk wrote:
% On Fri, Sep 07, 2012 at 02:46:34PM +0200, Jan Pazdziora wrote:
% I'm not sure I correctly understand what you ask about but the
% oracle_get_database_answers
%
% The /etc/rhn/rhn.conf has nothing to do with *Oracle* database at all.
% It is *generic* config and database
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
Hi!
I am wondering what was the reason to make this very awkward change in
1.7 by using URI in db_name in the /etc/rhn/rhn.conf other than
because now our Java can connect different way?
My opinion on that:
1. This is called *db_name*. So let it be the *name*.
2. This is not called db_uri as it
On Fri, Sep 07, 2012 at 02:22:56PM +0200, Bo Maryniuk wrote:
I am wondering what was the reason to make this very awkward change in
1.7 by using URI in db_name in the /etc/rhn/rhn.conf other than
because now our Java can connect different way?
I'm not sure I correctly understand what you ask
On Fri, Sep 07, 2012 at 02:46:34PM +0200, Jan Pazdziora wrote:
I'm not sure I correctly understand what you ask about but the
oracle_get_database_answers
The /etc/rhn/rhn.conf has nothing to do with *Oracle* database at all.
It is *generic* config and database back-end can be even IBM DB2 one
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
has nothing to
