Sybase::Simple - use database should be an option to the constructor?

[Terrence Brannon]

According to Mike, choosing a database is a separate step in
Sybase::Simple (which BTW is a godsend module).

However, I see no reason why it couldnt be an additional argument to new:

my $syb = Sybase::Simple->new($user, $password, undef, $database);

And certainly the DBI has the database_name as an argument to it's $dbh factory

Of course I could just subclass Sybase::Simple with a module that took
the additional argument and then made the call. But I honestly think
that most people would prefer that the standard Sybase::Simple offer
it.

With Sybase::Simple you'd do something like
$dbh->ExecSql("use $db");

Hi, it appears that Sybase::Simple does not have support for
connecting to a particular database after connecting to the server?

[Terrence Brannon]

Post by Terrence Brannon
According to Mike, choosing a database is a separate step in
Sybase::Simple (which BTW is a godsend module).
my $syb = Sybase::Simple->new($user, $password, undef, $database);

oops, forgot server:

my $syb = Sybase::Simple->new($user, $password, $server, $app, $database);

[Michael X Peppler]

Hi,

That's a pretty simple change really... maybe you could provide a patch?


Regards,
Michael Peppler

IPB Technology Build
***@jpmchase.com

-----Original Message-----
From: owner-sybperl-***@peppler.org [mailto:owner-sybperl-***@peppler.org] On Behalf Of Terrence Brannon
Sent: Tuesday, October 20, 2009 8:39 PM
To: sybperl-***@peppler.org
Subject: Re: Sybase::Simple - use database should be an option to the constructor?

Post by Terrence Brannon
According to Mike, choosing a database is a separate step in
Sybase::Simple (which BTW is a godsend module).
my $syb = Sybase::Simple->new($user, $password, undef, $database);

oops, forgot server:

my $syb = Sybase::Simple->new($user, $password, $server, $app, $database);
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.

Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to European legal entities.

[Terrence Brannon]

On Wed, Oct 21, 2009 at 1:47 AM, Michael X Peppler

Post by Michael X Peppler
Hi,
That's a pretty simple change really... maybe you could provide a patch?

If you put Sybase::Simple on github, I would be happy to fork and
supply a number of patches:

1 - I need a HashOfHashOfHashOfHash routine and have written it
2 - the methods really should check for required args instead of just
doing shift()
3 - it would be nice if you could navigate to each method from the
Table fo Contents of the POD by making each method a =head section