On Sat, Aug 1, 2009 at 2:15 AM, Darren Duncan wrote:
> But the point is that $dbh is a *DBD::SQLite* object, that *does* DBI, not
> *is* a DBI object that wraps the driver.
I second that point. IMO, one of the most difficult things to
understand for driver authors with nowadays DBI is the differe
On 4/30/07, Tim Bunce <[EMAIL PROTECTED]> wrote:
If the driver can make the handle truely read-only (by issing a statement like
"C" as needed, for example) then it should.
Otherwise the attribute is simply advisory.
For reading the value, I agree. I'd like to see a third value when
writing. Th
Tim Bunce wrote:
No doubt someone will quote the relevant parts. (And no doubt the
relevant parts will say "it depends" :)
I believe, the "no doubt" part is showing your age, aka experience. :-)
On 11/15/05, Tyler MacDonald <[EMAIL PROTECTED]> wrote:
> But it's licensed under the GPL, so if I wrote my package using it,
> I would be encumbered by the GPL by proxy. :-/
You're most definitely using a real lot of modules, which are have
perl's dual license, one of them being the GPL.
Jonathan Leffler wrote:
Oh drat - not the DBI connection string discussion again!
;-)
Jonathan Leffler wrote:
Can you explain which parts of the SQL:2003 mandate this notation? I've had
a moderately good poke around my copy of ISO/IEC 9075-2:2003
(SQL/Foundation) and cannot find this. I'd like a few section numbers listed
which describe this.
I second that one too. Besides, I
Jonathan Leffler wrote:
I dunno which DBMS support prepare without a database connection, but I
would expect all the mainstream databases to require a database connection.
+1
I'm also far from convinced that there's any significant benefit in
separating the 'create a database handle' from t
On Thu, 13 Jan 2005 00:40:49 -0600, David Nicol <[EMAIL PROTECTED]> wrote:
> Am I missing something?
Yes, to convince, at least me. I still don't understand, what this
should be good for. If it is fine for you, with a limited number of
drivers supported, then you may very well use it. You may as
I'm having a problem utilizing the perl DBI::Proxy to go between a
UNIX (Solaris)
and a Windows SQL server. We started getting an error message
"Error while reading socket: Connection reset by peer at
/usr/local/lib/perl5/site_perl/5.6.1/RPC/PlServer/Comm.pm line 110."
that I can't seem to r
Alan Burlison wrote:
One other question - how do I get the parent DBH from a STH from
within the XS code for a DBD driver?
There's a DBI macro for that, I do not remember the name, but most
probably its DBIxxx_parent or similar.
Hi, Steve,
[...]
> The problem is: How do I trap all input/output to/from DBI to do these
> conversions?
[...]
> I've asked about this on the dbi-users mailing list, and the answer
> (from Tim Bunce, no less) was that it is really the responsibility of
> the DBD driver to perform such conv
Quoting Tim Bunce <[EMAIL PROTECTED]>:
> p.s. To all: I _think_ Jochen, the author of Net::Deamon and the PlRPC
> modules is interested in finding someone willing and able to take
> over their maintenance. Anyone interested should contact Jochen [CC'd].
Damn bloody right! :-)
Quoting Jeff Urlwin <[EMAIL PROTECTED]>:
> I don't have a problem with that, in principle. I guess I could talk
> to
> Jenda Krynicky (sp) too, since he seems to have some modules up and
> seems to
> use DBI. I don't know Randy, can you send me an e-mail address or
> contact
> information?
Se
Hi, Jeff,
Quoting Jeff Urlwin <[EMAIL PROTECTED]>:
> Jochen -- I agree with you, but until someone gets Oracle to write it
> to ActiveState or ActiveState works it out with Oracle, I'll do the
> best I can.
of course I wasn't aware of such legal nonsense. My apologize,
in that case I can of cou
Hi, Jeff,
Quoting Jeff Urlwin <[EMAIL PROTECTED]>:
> One thing to keep in mind is that you *should* get your binary built
> modules
> from the same location. So, if you want DBD::Oracle, make sure you get
> DBI from my site.
this is what bothers me. First of all, note that the current release
Zitiere Christian Jaeger <[EMAIL PROTECTED]>:
> Hello
>
> There is also another bug:
>
> connect with autocommit 0ff.
> restart mysql
> $DB->commit; # This time it will *NOT* give an error. It seems
># that this commit is silently optimized away by
It is not optimized, it is due
Please try the following patch, to be found in
DBD::mysql 2.1006:
--- dbdimp.c~ Thu Dec 13 09:58:07 2001
+++ dbdimp.cThu Dec 27 18:45:25 2001
@@ -1951,6 +1951,15 @@
/* Other error */
return FALSE;
}
+
+ if (DBIc_has(imp_dbh, DBIcf_AutoCommit)) {
+/* We never reconnect if
y:
2001-12-13 Jochen Wiedmann <[EMAIL PROTECTED]> (2.1005)
* dbdimp.c: Added use of SvMAGICAL to dbd_db_quote.
Rudy Lippan <[EMAIL PROTECTED]>
Yours sincerely,
Jochen
Hi, Tim,
Zitiere Tim Bunce <[EMAIL PROTECTED]>:
> Er, why not fix Storable to be thread safe (if it isn't).
> That's bound to be fairly trivial and Storable is many times
> faster than Data::Dumper.
making Storable thread safe is harder than you might
think. I have once sent a patch to Raphael
Zitiere Simon Oliver <[EMAIL PROTECTED]>:
> iThreads is supposed to emulate fork on Win32 but this doesn't work for
> extensions that are not thread safe; this includes "Storable" which
> happens
> to be used by the PlRPC modules.
It should be comparatively simple to replace Storable
with Data:
Quoting [EMAIL PROTECTED]:
> Can't call method "tid" on an undefined value at
> c:/Perl/site/lib/Net/Daemon/Log.pm line 75
Strange, Thread->self seems to return undef under ActivePerl ...
Well, please try Net::Daemon 0.36, which I have uploaded to
CPAN some minutes ago. That problem should be h
Hello,
I'd like to announce the release of DBD::mysql 2. This software
is considered experimental and should not be used in production
environments. The target is to collect feedback.
DBD::mysql is a successor of the former Msql-Mysql-modules.
About 4 years ago I have merged DBD::mSQL and DBD::
Alex Hornby wrote:
> In DBD/File.pm which ships as part of DBD::CSV there is an opendir
> without a closedir, which results in a file descriptor leak.
I believe you and will release a new version today. However, if you
are right, the problem is more suspicious to be a bug in Perl,
because the
tarts using the transaction support, should read
the section on TRANSACTION SUPPORT in the docs, which I also
add below. You can recall it at any time with
perldoc DBD::mysql.
Thanks to all of those who sent patches. I apologize for waiting
so long to apply them.
Yours,
Jochen
2001-04-01 J
24 matches
Mail list logo
