> Here's what the DBD::Oracle documentation has to say on the topic:
>
> > In Oracle, the concept of user and schema is (currently) the same.
Because
> > database objects are owned by an user, the owner names in the data
dictionary
> > views correspond to schema names. Oracle does not suppor
On 3/1/06 12:52 AM, Ron Savage wrote:
> On Wed, 01 Mar 2006 00:23:28 -0500, John Siracusa wrote:
>> Should it be a fatal error on the call to register_db if schema doesn't match
>> username when the driver is Oracle?
>
> Might as well be fatal, if that's what it's going to take to get all this to
On Wed, 01 Mar 2006 00:23:28 -0500, John Siracusa wrote:
Hi John
> It wouldn't, since no other Rose::DB driver class would return true
> from its use_username_if_schema_is_undef_in_pk_info_calls() or
> whatever crazy name I'd come up with :)
Ahh, I see. That's fine by me.
> Hm, okay. But what
On 3/1/06 12:03 AM, Ron Savage wrote:
> I would not want code inside Rose to say the schema param to primary_key_info
> (or any method, actually) comes from $self -> schema || $self -> username.
> What about another vendor where it has to be undef, and schema is undef, and
> username is set, as usu
On Tue, 28 Feb 2006 22:44:48 -0500, John Siracusa wrote:
Hi John
> On 2/28/06 9:37 PM, Ron Savage wrote:
>> The only call to primary_key_info I found is in
>> Rose::DB::Object::Metadata::Auto, which will presumably just
>> work, since it ultimately calls $db->schema, and the new docs
>> will have
On 2/28/06 9:37 PM, Ron Savage wrote:
> The only call to primary_key_info I found is in
> Rose::DB::Object::Metadata::Auto, which will presumably just work, since it
> ultimately calls $db->schema, and the new docs will have told the user to set
> schema appropriately for Oracle, right?
I really d
On Tue, 28 Feb 2006 20:33:34 -0500, John Siracusa wrote:
Hi John
> "Any Rose::DB object method that sets a data source configuration
> value is a valid parameter name."
Well, yes, but it's been decades since I tried to memorize /all/ the
documentation for a project.
> Hm, I wonder if that's a f
On 2/28/06 8:14 PM, Ron Savage wrote:
> o If I want to set the schema I can do that in the call to
> Rose::DB->register_db, just as I can with driver, database, etc, although I
> have not yet found a Rose doc indicating this was possible
http://search.cpan.org/dist/Rose-DB/lib/Rose/DB.pm#register_
Hi Folks
OK. I ran a series of tests:
o If I want to set the schema I can do that in the call to
Rose::DB->register_db, just as I can with driver, database, etc, although I have
not yet found a Rose doc indicating this was possible
o list_tables doesn't need a schema. All of:
- undef
On 2/28/06 10:58 AM, Rob Kinyon wrote:
> On 2/28/06, John Siracusa <[EMAIL PROTECTED]> wrote:
>> Okay, but what about the list_tables() situation? Should it pass the
>> schema value or wildcard with %?
>
> Are you looking for all tables with that name in any schema that your
> user has access to
On 2/28/06, John Siracusa <[EMAIL PROTECTED]> wrote:
> On 2/28/06 9:46 AM, Rob Kinyon wrote:
> > Schema should default to username, but should be overridable. In other
> > words, set it as normal, but in the intializer, set it to username if
> > unset.
>
> Okay, but what about the list_tables() si
On 2/28/06 9:46 AM, Rob Kinyon wrote:
> Schema should default to username, but should be overridable. In other
> words, set it as normal, but in the intializer, set it to username if
> unset.
Okay, but what about the list_tables() situation? Should it pass the
schema value or wildcard with %?
-
On 2/28/06, John Siracusa <[EMAIL PROTECTED]> wrote:
> Ron Savage is working on Oracle support for Rose::DB. He's currently
> implicitly setting the schema() to the username(), but I'm not sure that's
> such a great idea. Where we run into problems is in the list_tables()
> method where the schem
Ron Savage is working on Oracle support for Rose::DB. He's currently
implicitly setting the schema() to the username(), but I'm not sure that's
such a great idea. Where we run into problems is in the list_tables()
method where the schema arg apparently can't be left blank:
$dbh->table_info($
14 matches
Mail list logo
