<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>http://groups.google.com.au/group/perl.dbi.dev</id>
  <title type="text">perl.dbi.dev Google Group</title>
  <subtitle type="text">
  dbi-dev@perl.org (Moderated)
  </subtitle>
  <link href="/group/perl.dbi.dev/feed/atom_v1_0_msgs.xml" rel="self" title="perl.dbi.dev feed"/>
  <updated>2009-12-08T16:18:11Z</updated>
  <generator uri="http://groups.google.com.au" version="1.99">Google Groups</generator>
  <entry>
  <author>
  <name>Praveen</name>
  <email>praveen...@in.ibm.com</email>
  </author>
  <updated>2009-12-08T05:19:29Z</updated>
  <id>http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/0c75189071024a92/822f0fa00198581a?show_docid=822f0fa00198581a</id>
  <link href="http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/0c75189071024a92/822f0fa00198581a?show_docid=822f0fa00198581a"/>
  <title type="text">Re: ANNOUNCE: IBM DB2 Database Driver for Perl DBI Version 1.74 released</title>
  <summary type="html" xml:space="preserve">
  Hi, &lt;br&gt; A typo, &lt;br&gt; Please read the version as 1.76 in the subject line. &lt;br&gt; Thanks and Regards &lt;br&gt; Praveen &lt;br&gt; Open Source Application Development &lt;br&gt; IBM India Software Labs
  </summary>
  </entry>
  <entry>
  <author>
  <name>Tim Bunce</name>
  <email>tim.bu...@pobox.com</email>
  </author>
  <updated>2009-12-08T16:18:11Z</updated>
  <id>http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/88acea856b1f4b83/17c71ab9c9499dd5?show_docid=17c71ab9c9499dd5</id>
  <link href="http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/88acea856b1f4b83/17c71ab9c9499dd5?show_docid=17c71ab9c9499dd5"/>
  <title type="text">Re: sql_type_cast small inconsistency and bugs</title>
  <summary type="html" xml:space="preserve">
  That PurePerl one I did was just a rough sketch. &lt;br&gt; use warnings FATAL =&amp;gt; qw(numeric); is s nice approach. &lt;br&gt; I don&#39;t think that&#39;ll affect the minimum perl version (5.8.1) &lt;br&gt; The lack of difference in the code between SQL_DOUBLE and SQL_NUMERIC is &lt;br&gt; a little troubling, though I&#39;ve no time to think about it right now.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Martin Evans</name>
  <email>martin.ev...@easysoft.com</email>
  </author>
  <updated>2009-12-08T13:32:33Z</updated>
  <id>http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/88acea856b1f4b83/5c0a88b74fb9c908?show_docid=5c0a88b74fb9c908</id>
  <link href="http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/88acea856b1f4b83/5c0a88b74fb9c908?show_docid=5c0a88b74fb9c908"/>
  <title type="text">Re: sql_type_cast small inconsistency and bugs</title>
  <summary type="html" xml:space="preserve">
  Done and one last (I&#39;m hoping) thing. The PurePerl version that was &lt;br&gt; added does not match the XS version as the success of the cast (or not) &lt;br&gt; is not reflected in the return value. The following change fixes it but &lt;br&gt; I&#39;d rather see some comment on it before committing: &lt;br&gt; Index: lib/DBI/PurePerl.pm &lt;br&gt; ============================== ============================== =======
  </summary>
  </entry>
  <entry>
  <author>
  <name>Tim Bunce</name>
  <email>tim.bu...@pobox.com</email>
  </author>
  <updated>2009-12-08T12:47:14Z</updated>
  <id>http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/88acea856b1f4b83/d36aa279512cac58?show_docid=d36aa279512cac58</id>
  <link href="http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/88acea856b1f4b83/d36aa279512cac58?show_docid=d36aa279512cac58"/>
  <title type="text">Re: sql_type_cast small inconsistency and bugs</title>
  <summary type="html" xml:space="preserve">
  Quite possibly. &lt;br&gt; Let&#39;s just skip for perl &amp;lt; 5.10.1. &lt;br&gt; Tim.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Martin Evans</name>
  <email>martin.ev...@easysoft.com</email>
  </author>
  <updated>2009-12-08T12:04:25Z</updated>
  <id>http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/88acea856b1f4b83/26b296810839c002?show_docid=26b296810839c002</id>
  <link href="http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/88acea856b1f4b83/26b296810839c002?show_docid=26b296810839c002"/>
  <title type="text">Re: sql_type_cast small inconsistency and bugs</title>
  <summary type="html" xml:space="preserve">
  I&#39;ve looked in to this a little more now and it appears this fails for &lt;br&gt; Perl &amp;lt; 5.10.1 and works for 5.10.1 so I&#39;m guessing something in svc.c &lt;br&gt; has changed between those releases. Probably the code you looked at was &lt;br&gt; the latest source? &lt;br&gt; Perhaps it was something to do with: &lt;br&gt; ï¿½ The public IV and NV flags are now not set if the string
  </summary>
  </entry>
  <entry>
  <author>
  <name>Open Source Application Development</name>
  <email>open...@us.ibm.com</email>
  </author>
  <updated>2009-12-07T12:49:31Z</updated>
  <id>http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/0c75189071024a92/4e2a5f9f2a52faa1?show_docid=4e2a5f9f2a52faa1</id>
  <link href="http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/0c75189071024a92/4e2a5f9f2a52faa1?show_docid=4e2a5f9f2a52faa1"/>
  <title type="text">ANNOUNCE: IBM DB2 Database Driver for Perl DBI Version 1.74 released</title>
  <summary type="html" xml:space="preserve">
  IBM DB2 Database Driver for Perl DBI Version 1.76 has been uploaded on &lt;br&gt; CPAN. Testers are please welcome to test the new features and report the &lt;br&gt; bugs. &lt;br&gt; DBI is an open standard application programming interface (API) that &lt;br&gt; provides database access for client applications written in Perl. DBI &lt;br&gt; defines a set of functions, variables, and conventions that provide a
  </summary>
  </entry>
  <entry>
  <author>
  <name>Tim Bunce</name>
  <email>tim.bu...@pobox.com</email>
  </author>
  <updated>2009-12-05T14:27:43Z</updated>
  <id>http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/159c08bb415a0c66/471c04eb0880c57f?show_docid=471c04eb0880c57f</id>
  <link href="http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/159c08bb415a0c66/471c04eb0880c57f?show_docid=471c04eb0880c57f"/>
  <title type="text">Re: DBI svn 13624 not very healthy</title>
  <summary type="html" xml:space="preserve">
  I&#39;ve done that bit now. &lt;br&gt; Tim.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Tim Bunce</name>
  <email>tim.bu...@pobox.com</email>
  </author>
  <updated>2009-12-04T21:47:17Z</updated>
  <id>http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/159c08bb415a0c66/83dc2db16da84905?show_docid=83dc2db16da84905</id>
  <link href="http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/159c08bb415a0c66/83dc2db16da84905?show_docid=83dc2db16da84905"/>
  <title type="text">Re: DBI svn 13624 not very healthy</title>
  <summary type="html" xml:space="preserve">
  Sorry for the delay. I&#39;ve been tied up with progressing some work on plperl &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.mail-archive.com/pgsql-hack...@postgresql.org/msg140671.html&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.mail-archive.com/pgsql-hack...@postgresql.org/msg140769.html&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; I hope to get to this in the next few days. &lt;br&gt; The t/zv*_*.t tests are wrappers for the main tests. They&#39;re written by
  </summary>
  </entry>
  <entry>
  <author>
  <name>H.Merijn Brand</name>
  <email>h.m.br...@xs4all.nl</email>
  </author>
  <updated>2009-12-04T12:22:15Z</updated>
  <id>http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/fbfb030213848836/dfd787a76b437e0d?show_docid=dfd787a76b437e0d</id>
  <link href="http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/fbfb030213848836/dfd787a76b437e0d?show_docid=dfd787a76b437e0d"/>
  <title type="text">Re: Implementing file-locking *control* in DBD::File</title>
  <summary type="html" xml:space="preserve">
  On Fri, 4 Dec 2009 13:03:00 +0100, Jens Rehsack &lt;br&gt; I just extended what was already there: hard-coded numbers. &lt;br&gt; Yes, but it will also slow down. Given that string compares take longer &lt;br&gt; than numeric compares, and that we will have to do a lot more checking &lt;br&gt; (like only accept the spelling/casing we would accept) in several
  </summary>
  </entry>
  <entry>
  <author>
  <name>Jens Rehsack</name>
  <email>rehs...@googlemail.com</email>
  </author>
  <updated>2009-12-04T12:03:00Z</updated>
  <id>http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/fbfb030213848836/8706e0aa8ab5a8cd?show_docid=8706e0aa8ab5a8cd</id>
  <link href="http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/fbfb030213848836/8706e0aa8ab5a8cd?show_docid=8706e0aa8ab5a8cd"/>
  <title type="text">Re: Implementing file-locking *control* in DBD::File</title>
  <summary type="html" xml:space="preserve">
  2009/12/4 H.Merijn Brand &amp;lt;h.m.br...@xs4all.nl&amp;gt;: &lt;br&gt; I wouldn&#39;t use the numbers 0..2 - I&#39;d suggest using LOCK_SH, LOCK_EX &lt;br&gt; etc. instead. &lt;br&gt; This will help if any (exotic) OS defines it in the upper half byte or so. &lt;br&gt; NON_BLOCK: &lt;br&gt; [...] &lt;br&gt; ERRORS &lt;br&gt; The flock() system call fails if: &lt;br&gt; [EWOULDBLOCK]	The file is locked and the LOCK_NB option was specified.
  </summary>
  </entry>
  <entry>
  <author>
  <name>H.Merijn Brand</name>
  <email>h.m.br...@xs4all.nl</email>
  </author>
  <updated>2009-12-04T10:38:49Z</updated>
  <id>http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/fbfb030213848836/c144f009e211d6a2?show_docid=c144f009e211d6a2</id>
  <link href="http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/fbfb030213848836/c144f009e211d6a2?show_docid=c144f009e211d6a2"/>
  <title type="text">Re: Implementing file-locking *control* in DBD::File</title>
  <summary type="html" xml:space="preserve">
  On Fri, 4 Dec 2009 10:03:54 +0100, Jens Rehsack &lt;br&gt; That can still be done. You can set a localized $data-&amp;gt;{Database}{f_lock} &lt;br&gt; What I have now done (and committed) is create support and &lt;br&gt; documentation for locking control. How this will be used is up to the &lt;br&gt; higher levels. &lt;br&gt; LOCK_NB? &lt;br&gt; Apply or remove an advisory lock on the open file specified by fd. The
  </summary>
  </entry>
  <entry>
  <author>
  <name>Jens Rehsack</name>
  <email>rehs...@googlemail.com</email>
  </author>
  <updated>2009-12-04T09:03:54Z</updated>
  <id>http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/fbfb030213848836/48fe61b7bc062e3e?show_docid=48fe61b7bc062e3e</id>
  <link href="http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/fbfb030213848836/48fe61b7bc062e3e?show_docid=48fe61b7bc062e3e"/>
  <title type="text">Re: Implementing file-locking *control* in DBD::File</title>
  <summary type="html" xml:space="preserve">
  2009/12/3 H.Merijn Brand &amp;lt;h.m.br...@xs4all.nl&amp;gt;: &lt;br&gt; While the originator of this request updates his ticket, maybe a smarter &lt;br&gt; implementation is reasonable: &lt;br&gt; I could modify S::S opentable() to request opening for reading/writing, &lt;br&gt; so you could differ between LOCK_SH and LOCK_EX automatically. &lt;br&gt; Further, it could be suitable to or LOCK_NB, which allows to avoid deadlocks.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Martin J. Evans</name>
  <email>martin.ev...@easysoft.com</email>
  </author>
  <updated>2009-12-03T20:01:08Z</updated>
  <id>http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/159c08bb415a0c66/6cb73017216bc60d?show_docid=6cb73017216bc60d</id>
  <link href="http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/159c08bb415a0c66/6cb73017216bc60d?show_docid=6cb73017216bc60d"/>
  <title type="text">Re: DBI svn 13624 not very healthy</title>
  <summary type="html" xml:space="preserve">
  This latter one is fixed now. I was checking $Config{longsize} and have &lt;br&gt; changed it to $Config{ivsize}. Thanks to Tux for pointing it out and &lt;br&gt; testing the fix. &lt;br&gt; &amp;lt;snipped&amp;gt; &lt;br&gt; &amp;lt;snipped&amp;gt; &lt;br&gt; Perhaps Tim can tell me how to fix that. &lt;br&gt; Martin
  </summary>
  </entry>
  <entry>
  <author>
  <name>H.Merijn Brand</name>
  <email>h.m.br...@xs4all.nl</email>
  </author>
  <updated>2009-12-03T18:30:30Z</updated>
  <id>http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/159c08bb415a0c66/004446ab5b1349d8?show_docid=004446ab5b1349d8</id>
  <link href="http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/159c08bb415a0c66/004446ab5b1349d8?show_docid=004446ab5b1349d8"/>
  <title type="text">Re: DBI svn 13624 not very healthy</title>
  <summary type="html" xml:space="preserve">
  On Thu, 03 Dec 2009 17:35:50 +0000, Martin Evans &lt;br&gt; Summary of my perl5 (revision 5 version 10 subversion 0) configuration: &lt;br&gt; Platform: &lt;br&gt; osname=linux, osvers=2.6.22.13-0.3-default, archname=i686-linux-64int &lt;br&gt; uname=&#39;linux nb09 2.6.22.13-0.3-default #1 smp 20071119 15:02:58 utc i686 i686 i386 gnulinux &#39;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Martin Evans</name>
  <email>martin.ev...@easysoft.com</email>
  </author>
  <updated>2009-12-03T17:35:50Z</updated>
  <id>http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/159c08bb415a0c66/fa3c9bc90207f4d4?show_docid=fa3c9bc90207f4d4</id>
  <link href="http://groups.google.com.au/group/perl.dbi.dev/browse_frm/thread/159c08bb415a0c66/fa3c9bc90207f4d4?show_docid=fa3c9bc90207f4d4"/>
  <title type="text">Re: DBI svn 13624 not very healthy</title>
  <summary type="html" xml:space="preserve">
  I&#39;d expect those 2 at the moment as there is an outstanding issue with &lt;br&gt; Perl_sv_2nv. I left them in so if Tim had any time he could see them. &lt;br&gt; What platform did you run this test on - a 64bit platform? Can you email &lt;br&gt; me your Perl -V. &lt;br&gt; I don&#39;t really know how/why each test is duplicated with different &lt;br&gt; prefixes in those below - I don&#39;t get that.
  </summary>
  </entry>
</feed>
