Fabio Telles wrote:
In Oracle, we use the clause 'set role identified by some_password'.
How could I handle these problem. Any clue?
Normally these role passwords in Oracle are used (and stored) on a
middle tier, and not put into the hands of the client. So where are you
storing this role pass? Compiling it into the app and hoping no one
runs strings on it (or whatever level of digging is required)?
Paul
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
