On Tue, Nov 30, 2004 at 11:02:31PM -0600, David Nicol wrote:
instead of having to haul around the code to figure this out, why not create a
handy documentary web service somewhere where you fill out the blanks and
get an appropriate connection string? Loading a module every time you start
the
Tim Bunce wrote on 30 November 2004 23:32
On Tue, Nov 30, 2004 at 09:38:47PM +, Nicholas Clark wrote:
On Tue, Nov 30, 2004 at 08:53:51PM +, Tim Bunce wrote:
I don't get it. Can someone give me some small but real examples
of the problem that's being solved here?
The one
On Wed, Dec 01, 2004 at 09:46:24AM +, Tim Bunce wrote:
Do you generally pass URLs around as a string or broken up into a hash?
If I have to deal with query strings in Perl, I do prefer to deal with
them as hash, and then use CGI.pm to re-stringify it for me as needed.
Mark
On Wed, Dec 01, 2004 at 09:56:01AM -0500, John Siracusa wrote:
On Wed, 1 Dec 2004 09:46:24 +, Tim Bunce [EMAIL PROTECTED] wrote:
Do you generally pass URLs around as a string or broken up into a hash?
If they had different formats for different consumers, I would. (And even
today, I
It'll always come down to the issue of why not store complete DSNs?
and so far that's not been well covered by the feedback I've got.
Duplication of data in multiple places is the answer I think. The more DSN
strings you have the more needs to be changed later on, and the bigger the
chance
On Wed, 1 Dec 2004 18:39:00 +, Tim Bunce [EMAIL PROTECTED] wrote:
FWIW, the reason I'm digging here is because I agree there may be
some value in the DBI supporting something along these lines, but
I need a better understanding of the underlying issues. More real-
world examples would
On Wed, Dec 01, 2004 at 06:43:51PM -, Orton, Yves wrote:
It'll always come down to the issue of why not store complete DSNs?
and so far that's not been well covered by the feedback I've got.
Duplication of data in multiple places is the answer I think. The more DSN
strings you have
