<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.python.db.pysqlite.user">
    <title>gmane.comp.python.db.pysqlite.user</title>
    <link>http://blog.gmane.org/gmane.comp.python.db.pysqlite.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2358"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2357"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2356"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2355"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2354"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2353"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2352"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2351"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2350"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2349"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2348"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2347"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2346"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2345"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2358">
    <title>Re: [pysqlite] This group will move over to Google Groups</title>
    <link>http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2358</link>
    <description>&lt;pre&gt;

Roger,

   The invitation arrived and I responded appropriately.

Thanks,

Rich
&lt;/pre&gt;</description>
    <dc:creator>Rich Shepard</dc:creator>
    <dc:date>2009-10-18T18:55:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2357">
    <title>Re: [pysqlite] This group will move over to Google Groups</title>
    <link>http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2357</link>
    <description>&lt;pre&gt;
They have just been approved.  We can close this list to new posts now.

For those doing mail filtering the new group has a subject prefix of
[python-sqlite].  I have notified the Gmane admins of the changes but
they haven't followed up on them yet.

Roger
&lt;/pre&gt;</description>
    <dc:creator>Roger Binns</dc:creator>
    <dc:date>2009-10-18T17:13:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2356">
    <title>Re: [pysqlite] This group will move over to Google Groups</title>
    <link>http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2356</link>
    <description>&lt;pre&gt;
You should receive an email asking you to join the group requiring you
to take some action to join.  (The interface does allow for just
directly adding people but that is what spammers do!)

Consequently you can just go ahead and add yourself without waiting for
the invitation.  You haven't missed anything yet except the announcement
of APSW 3.6.19 which now includes an awesome shell :-)

Roger
&lt;/pre&gt;</description>
    <dc:creator>Roger Binns</dc:creator>
    <dc:date>2009-10-18T17:02:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2355">
    <title>Re: [pysqlite] This group will move over to Google Groups</title>
    <link>http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2355</link>
    <description>&lt;pre&gt;

Gerhard,

   When the Google admins approve the invitations are we automatically
subscribed to the new group/mail list?

Thanks,

Rich

&lt;/pre&gt;</description>
    <dc:creator>Rich Shepard</dc:creator>
    <dc:date>2009-10-18T15:07:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2354">
    <title>Re: [pysqlite] This group will move over to Google Groups</title>
    <link>http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2354</link>
    <description>&lt;pre&gt;
I just invited all 149 list subscribers. This looked suspicious to
Google so the invitation is now waiting for approval by Google admins.
Once that is done you will receive the invitation email.

Or you can just subscribe manually of course.

&lt;/pre&gt;</description>
    <dc:creator>Gerhard Häring</dc:creator>
    <dc:date>2009-10-18T09:04:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2353">
    <title>Re: [pysqlite] This group will move over to Google Groups</title>
    <link>http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2353</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gerhard Häring wrote:

Those of you whose German is not very good may prefer this link :-)

  http://groups.google.com/group/python-sqlite

Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkra01UACgkQmOOfHg372QTpJACfVbUWRsfYK3VOgfyXy0h5Z0dR
5GQAnR64Scx5hhNHZu0gwUuKw22A4fff
=ZjlM
-----END PGP SIGNATURE-----
&lt;/pre&gt;</description>
    <dc:creator>Roger Binns</dc:creator>
    <dc:date>2009-10-18T08:35:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2352">
    <title>[pysqlite] This group will move over to Google Groups</title>
    <link>http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2352</link>
    <description>&lt;pre&gt;Hello,

I was guilty of a misconfiguration of the  mail server this list is
hosted on. The effect was that the only subscriber that received mails
from the list for a month or so were members subscribed to the domain
ghaering.de. I. e. only me.

So I decided to outsource the administration problems to Google. This
mailing list will move over to Google Groups (Roger Binns already set a
group up there):

http://groups.google.de/group/python-sqlite

I'll invite all subscribers of this list in a few minutes.

I will move the pysqlite hosting to Google Code during the next days, too.

&lt;/pre&gt;</description>
    <dc:creator>Gerhard Häring</dc:creator>
    <dc:date>2009-10-18T08:33:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2351">
    <title>Re: [pysqlite] :memory: db</title>
    <link>http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2351</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dinesh B Vadhia wrote:

Why don't you try it with your data and your queries?  Also see
http://www.sqlite.org/pragma.html which lets you alter the default
SQLite cache sizes.

Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkqgaXwACgkQmOOfHg372QRcdQCgnSW16piQWw3wzVemmQZiPyun
XDoAoKKFgLekSXg9Hm072h9zEqEH2JNt
=nBQX
-----END PGP SIGNATURE-----
&lt;/pre&gt;</description>
    <dc:creator>Roger Binns</dc:creator>
    <dc:date>2009-09-04T01:12:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2350">
    <title>[pysqlite] :memory: db</title>
    <link>http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2350</link>
    <description>&lt;pre&gt;_______________________________________________
list-pysqlite mailing list
list-pysqlite-FR6EJeJVuqdwc357pe9rcyQmJico6nz3epZhswDD4dQ&amp;lt; at &amp;gt;public.gmane.org
http://itsystementwicklung.de/cgi-bin/mailman/listinfo/list-pysqlite&lt;/pre&gt;</description>
    <dc:creator>Dinesh B Vadhia</dc:creator>
    <dc:date>2009-09-03T21:50:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2349">
    <title>Re: [pysqlite] [apsw] ReadOnlyError when closing read-only blobs?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2349</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Austin Bingham wrote:

It is indeed the "correct" behaviour.  It is SQLite that does this.  I
actually use this as part of the test suite since it was the only way I
could think of deliberately causing an error on a read only blob.

This is alluded to in
http://apsw.googlecode.com/svn/publish/blob.html#apsw.blob.close

I have since updated the documentation to mention this specific example
and blame SQLite :-)

Roger

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkqdJwgACgkQmOOfHg372QRAxACgvTATM5VxqF3Jptt0cUHIN7O4
FgMAn1u0oNh8BINEGi6gEnRcJEo0AjLy
=1iTy
-----END PGP SIGNATURE-----
&lt;/pre&gt;</description>
    <dc:creator>Roger Binns</dc:creator>
    <dc:date>2009-09-01T13:52:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2348">
    <title>[pysqlite] [apsw] ReadOnlyError when closing read-only blobs?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2348</link>
    <description>&lt;pre&gt;I've found that Blob.close() throws a ReadOnlyError if I've previously
attempted to perform a write on that blob. I was surprised by this,
but I wanted to see if this is expected behavior.

Here's code that demonstrates the issue:

  import apsw

  sql = '''
  CREATE TABLE IF NOT EXISTS data
  (id INTEGER PRIMARY KEY NOT NULL,
   data BLOB NOT NULL)'''

  conn = apsw.Connection('test.db')
  cur = conn.cursor()
  cur.execute(sql)
  cur.execute('INSERT INTO data VALUES(?,?)', (None, apsw.zeroblob(1000)))
  rowid = conn.last_insert_rowid()
  blob = conn.blobopen('main', 'data', 'data', rowid, False)

  # Attempt a write
  try:
    blob.write('x' * 10)
  except apsw.ReadOnlyError:
    # expected
    pass

  # This throws ReadOnlyError unexpectedly
  blob.close()

This is with version 3.6.16 on python 2.6.1.

Austin
&lt;/pre&gt;</description>
    <dc:creator>Austin Bingham</dc:creator>
    <dc:date>2009-09-01T13:09:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2347">
    <title>Re: [pysqlite] An error in installing pysqlite</title>
    <link>http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2347</link>
    <description>&lt;pre&gt;
Try executing the test from somewhere else. The test suite tries to
create a database file in the working directory. And your choice of
working directory was an unfortunate one, it seems ;-)

&lt;/pre&gt;</description>
    <dc:creator>Gerhard Häring</dc:creator>
    <dc:date>2009-08-13T09:22:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2346">
    <title>[pysqlite] An error in installing pysqlite</title>
    <link>http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2346</link>
    <description>&lt;pre&gt;Hi list,

     The install-source.txt file said to email this list if I  
encountered errors running pysqlite2.test.test(), but didn't encounter  
any errors during compilation or installation. So that's what I am  
doing.

Here's the error I encountered (it says there are nine of them....but  
they sure seem related):

################################

[GCC 4.0.1 (Apple Inc. build 5465)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
 &amp;gt;&amp;gt;&amp;gt; from pysqlite2 import test
 &amp;gt;&amp;gt;&amp;gt; test.test()
.....................................................................................................................................................................EEEEEEEEE 
.................................
======================================================================
ERROR: CheckDMLdoesAutoCommitBefore  
(pysqlite2.test.transactions.TransactionTests)
----------------------------------------------------------------------
Traceback (most recent call last):
   File "/Library/Python/2.5/site-packages/pysqlite2/test/ 
transactions.py", line 38, in setUp
     self.con1 = sqlite.connect(get_db_path(), timeout=0.1)
OperationalError: unable to open database file

======================================================================
ERROR: CheckDeleteStartsTransaction  
(pysqlite2.test.transactions.TransactionTests)
----------------------------------------------------------------------
Traceback (most recent call last):
   File "/Library/Python/2.5/site-packages/pysqlite2/test/ 
transactions.py", line 38, in setUp
     self.con1 = sqlite.connect(get_db_path(), timeout=0.1)
OperationalError: unable to open database file

======================================================================
ERROR: CheckInsertStartsTransaction  
(pysqlite2.test.transactions.TransactionTests)
----------------------------------------------------------------------
Traceback (most recent call last):
   File "/Library/Python/2.5/site-packages/pysqlite2/test/ 
transactions.py", line 38, in setUp
     self.con1 = sqlite.connect(get_db_path(), timeout=0.1)
OperationalError: unable to open database file

======================================================================
ERROR: CheckLocking (pysqlite2.test.transactions.TransactionTests)
----------------------------------------------------------------------
Traceback (most recent call last):
   File "/Library/Python/2.5/site-packages/pysqlite2/test/ 
transactions.py", line 38, in setUp
     self.con1 = sqlite.connect(get_db_path(), timeout=0.1)
OperationalError: unable to open database file

======================================================================
ERROR: CheckRaiseTimeout (pysqlite2.test.transactions.TransactionTests)
----------------------------------------------------------------------
Traceback (most recent call last):
   File "/Library/Python/2.5/site-packages/pysqlite2/test/ 
transactions.py", line 38, in setUp
     self.con1 = sqlite.connect(get_db_path(), timeout=0.1)
OperationalError: unable to open database file

======================================================================
ERROR: CheckReplaceStartsTransaction  
(pysqlite2.test.transactions.TransactionTests)
----------------------------------------------------------------------
Traceback (most recent call last):
   File "/Library/Python/2.5/site-packages/pysqlite2/test/ 
transactions.py", line 38, in setUp
     self.con1 = sqlite.connect(get_db_path(), timeout=0.1)
OperationalError: unable to open database file

======================================================================
ERROR: CheckRollbackCursorConsistency  
(pysqlite2.test.transactions.TransactionTests)
----------------------------------------------------------------------
Traceback (most recent call last):
   File "/Library/Python/2.5/site-packages/pysqlite2/test/ 
transactions.py", line 38, in setUp
     self.con1 = sqlite.connect(get_db_path(), timeout=0.1)
OperationalError: unable to open database file

======================================================================
ERROR: CheckToggleAutoCommit  
(pysqlite2.test.transactions.TransactionTests)
----------------------------------------------------------------------
Traceback (most recent call last):
   File "/Library/Python/2.5/site-packages/pysqlite2/test/ 
transactions.py", line 38, in setUp
     self.con1 = sqlite.connect(get_db_path(), timeout=0.1)
OperationalError: unable to open database file

======================================================================
ERROR: CheckUpdateStartsTransaction  
(pysqlite2.test.transactions.TransactionTests)
----------------------------------------------------------------------
Traceback (most recent call last):
   File "/Library/Python/2.5/site-packages/pysqlite2/test/ 
transactions.py", line 38, in setUp
     self.con1 = sqlite.connect(get_db_path(), timeout=0.1)
OperationalError: unable to open database file

----------------------------------------------------------------------
Ran 207 tests in 0.083s

FAILED (errors=9)

#####################################

Thanks so much!

David
&lt;/pre&gt;</description>
    <dc:creator>David Garfield</dc:creator>
    <dc:date>2009-08-12T14:34:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2345">
    <title>[pysqlite] APSW 3.6.17-r1 released</title>
    <link>http://permalink.gmane.org/gmane.comp.python.db.pysqlite.user/2345</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

APSW 3.6.17-r1 is now available. The home page is at
http://code.google.com/p/apsw/ which includes full documentation, source
and binary distributions for Windows (Python 2.3 onwards including 3.0 &amp;amp;
3.1).

APSW is a wrapper around SQLite that provides all SQLite API
functionality in Python.  It is not DBAPI compliant as it provides
SQLite semantics.  pysqlite provides DBAPI semantics.  You can see the
two approaches contrasted at
http://apsw.googlecode.com/svn/publish/pysqlite.html

Changelist is below and a clickable version at
http://apsw.googlecode.com/svn/publish/changes.html

APSW has migrated from Subversion to Mercurial for source code control.
Hosting remains at Google Code

Updated a test due to VFS xUnlock errors now being ignored sometimes by
SQLite (SQLite ticket 3946).

The downloads page in the help didn’t mention the Windows Python 3.1 installer.

Running the test suite is now integrated into setup.py so you can do the
building and testing all in one go. Sample command line:

$ python setup.py install test

The test suite will now check the functionality of the FTS3, RTree and ICU
extensions if they were included. (The Windows binary distribution includes
FTS3 and RTree by default.)

Fixed issue 55 where FTS3 was unintentionally omitted from the Windows
binary distribution.

Various documentation updates.

Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkqBD9AACgkQmOOfHg372QSXtACggQZbyhdeYPqH7VF9CseQ+Lcm
En0An0t8i3wN4y8hZTUSlhT28Qq28Jop
=ZjOk
-----END PGP SIGNATURE-----
_______________________________________________
list-pysqlite mailing list
list-pysqlite&amp;lt; at &amp;gt;lists.itsystementwicklung.de
http://itsystementwicklung.de/cgi-bin/mailman/listinfo/list-pysqlite&lt;/pre&gt;</description>
    <dc:creator>Roger Binns</dc:creator>
    <dc:date>2009-08-11T06:29:40</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.python.db.pysqlite.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.python.db.pysqlite.user</link>
  </textinput>
</rdf:RDF>

