sqlobject-discuss — All things SQLObject-related

Re: [SQLObject] PostgreSQL warnings filling up the logs with PickleCol

[Oleg B. <ph...@ph...>]

Ok, found the problem - str() removes one level of backslashes so I have
to double backslashes once again. See the attached patch - it passes all
tests.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] PostgreSQL warnings filling up the logs with PickleCol

[Oleg B. <ph...@ph...>]

On Thu, May 31, 2012 at 11:35:31AM +0200, Tom Coetser <su...@ic...> wrote:
> On Thursday 31 May 2012 10:57:11 Oleg Broytman wrote:
> > On Thu, May 31, 2012 at 11:44:05AM +0400, Oleg Broytman <ph...@ph...> 
> wrote:
> > >    Can you apply and test the attached patch?
> > 
> >    Please be warned - the patch causes failures of test_blob,
> > test_picklecol and test_validation. Seems I have to investigate it
> > deeper.
> 
> Thanks for letting me know. So far unit tests on my app seems to be OK with 
> the patch, but I'll wait to hear more from your side before I deploy the 
> change.

   I use utf-8 encoding, and SQLObject tests generates binary data. The
reason for failures is that the patch makes SQLObject produce invalid
utf-8 sequences. If your databases and client/server encoding is ascii
or latin1 - I think the patch is ok.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] PostgreSQL warnings filling up the logs with PickleCol

[Tom C. <su...@ic...>]

Hi Oleg,

On Thursday 31 May 2012 10:57:11 Oleg Broytman wrote:
> On Thu, May 31, 2012 at 11:44:05AM +0400, Oleg Broytman <ph...@ph...> 
wrote:
> >    Can you apply and test the attached patch?
> 
>    Please be warned - the patch causes failures of test_blob,
> test_picklecol and test_validation. Seems I have to investigate it
> deeper.

Thanks for letting me know. So far unit tests on my app seems to be OK with 
the patch, but I'll wait to hear more from your side before I deploy the 
change.

Thanks,
 Tom

Re: [SQLObject] PostgreSQL warnings filling up the logs with PickleCol

[Oleg B. <ph...@ph...>]

On Thu, May 31, 2012 at 11:44:05AM +0400, Oleg Broytman <ph...@ph...> wrote:
>    Can you apply and test the attached patch?

   Please be warned - the patch causes failures of test_blob,
test_picklecol and test_validation. Seems I have to investigate it
deeper.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] PostgreSQL warnings filling up the logs with PickleCol

[Oleg B. <ph...@ph...>]

On Thu, May 31, 2012 at 10:31:33AM +0200, Tom Coetser <su...@ic...> wrote:
> Thanks, seems to solve the problem nicely. I assume this will go into the next 
> release for 1.3, correct?

   It will go to the repository today, but formal releases will be much
later. I'll be on vacation (and completely off-line) until June 20.

> > > Any help on how to solve this so I can get my log files cleaned up, in
> > > order to debug another connection problem, would be greatly appreciated.
> > 
> >    What log files? /var/log/postgresql/*.log?
> 
> Yes, but specifically /var/log/postgresql/postgresql-8.4-main.log on Debian 
> Squeeze.

/etc/init.d/postgresql stop
rm /var/log/postgresql/* # or rm *.gz && gzip *.log
/etc/init.d/postgresql start

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] PostgreSQL warnings filling up the logs with PickleCol

[Tom C. <su...@ic...>]

Hi Oleg,

Thanks for the quick reply.

On Thursday 31 May 2012 09:44:05 Oleg Broytman wrote:
> Hello!
> 
> On Thu, May 31, 2012 at 08:08:42AM +0200, Tom Coetser <su...@ic...> 
wrote:
> > I am getting a warning in the Postgres log for every time a PickleCol is
> > written to the database. Since my app uses a pickled col extensively in
> > one of the more frequently used tables, the Postgres logs are filled
> > with these warnings:
> > 
> > ----------------------
> > WARNING:  nonstandard use of \\ in a string literal at character 50
> > HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
> > ----------------------
> 
>    Thank you for an example of a good bug report! An error message and a
> short test case - exactly what I need.
>    Can you apply and test the attached patch?

Thanks, seems to solve the problem nicely. I assume this will go into the next 
release for 1.3, correct?

> > Any help on how to solve this so I can get my log files cleaned up, in
> > order to debug another connection problem, would be greatly appreciated.
> 
>    What log files? /var/log/postgresql/*.log?

Yes, but specifically /var/log/postgresql/postgresql-8.4-main.log on Debian 
Squeeze.


Again, thanks for the quick reply and fix. Much appreciated.


/Tom

Re: [SQLObject] PostgreSQL warnings filling up the logs with PickleCol

[Oleg B. <ph...@ph...>]

Hello!

On Thu, May 31, 2012 at 08:08:42AM +0200, Tom Coetser <su...@ic...> wrote:
> I am getting a warning in the Postgres log for every time a PickleCol is 
> written to the database. Since my app uses a pickled col extensively in one of 
> the more frequently used tables, the Postgres logs are filled with these 
> warnings:
> 
> ----------------------
> WARNING:  nonstandard use of \\ in a string literal at character 50
> HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
> ----------------------

   Thank you for an example of a good bug report! An error message and a
short test case - exactly what I need.
   Can you apply and test the attached patch?

> Any help on how to solve this so I can get my log files cleaned up, in order 
> to debug another connection problem, would be greatly appreciated.

   What log files? /var/log/postgresql/*.log?

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] PostgreSQL warnings filling up the logs with PickleCol

[Tom C. <su...@ic...>]

Hi all,

I am getting a warning in the Postgres log for every time a PickleCol is 
written to the database. Since my app uses a pickled col extensively in one of 
the more frequently used tables, the Postgres logs are filled with these 
warnings:

----------------------
WARNING:  nonstandard use of \\ in a string literal at character 50
HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
----------------------

This is with SQLObject v1.3.0, but it has been there from at least v0.12.4 
from which I am upgrading to 1.3.0 now.

PostgresSQL is v8.4.11 on Debian Squeeze.

An example test case to illustrate the problem is inline below.

Any help on how to solve this so I can get my log files cleaned up, in order 
to debug another connection problem, would be greatly appreciated.


Thanks,
 Tom



-------------------------------
from sqlobject import *

db = dict(user='tomc',
          passw='',
          host='',
          dbname='tomc')
dbURI = "postgres://%(user)s:%(passw)s@%(host)s/%(dbname)s" % db

connection = connectionForURI(dbURI)
sqlhub.processConnection = connection

# Default pickled data - try to use as many object types as possible for tests
defaultConfig = dict(ports=2,
                     remote=False,
                     logger=None,
                     services=['web', 'database'],
                     dns=dict(hostname=None,
                              domain='foo.bar')
                     )

# Define the sampe table with a pickled column
class Server(SQLObject):
    name = StringCol()
    config = PickleCol(notNull=True, default=defaultConfig)

# Drop and create table
Server.dropTable(ifExists=True)
Server.createTable()

# Turn on SQLObejct debugging
connection.debug=True

# Add test records while tailing the postgresql log files
s1 = Server(name='foo')
-------------------------------

[SQLObject] SQLObject 1.3.1

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 1.3.1, the first bug-fix release of branch
1.3 of SQLObject.


What is SQLObject
=================

SQLObject is an object-relational mapper.  Your database tables are described
as classes, and rows are instances of those classes.  SQLObject is meant to be
easy to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
http://pypi.python.org/pypi/SQLObject/1.3.1

News and changes:
http://sqlobject.org/News.html


What's New
==========

* Fixed a minor bug in PostgreSQL introspection: VIEWs don't have
  PRIMARY KEYs - use sqlmeta.idName as the key.

* Fixed a bug in cache handling while unpickling.

For a more complete list, please see the news:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] SQLObject 1.2.3

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 1.2.3, a bugfix release of branch
1.2 of SQLObject.


What is SQLObject
=================

SQLObject is an object-relational mapper.  Your database tables are described
as classes, and rows are instances of those classes.  SQLObject is meant to be
easy to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
http://pypi.python.org/pypi/SQLObject/1.2.3

News and changes:
http://sqlobject.org/News.html


What's New
==========

* Fixed a minor bug in PostgreSQL introspection: VIEWs don't have
  PRIMARY KEYs - use sqlmeta.idName as the key.

* Fixed a bug in cache handling while unpickling.

For a more complete list, please see the news:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Select Single Random Record

[Petr J. <pet...@tp...>]

>
>
> Ah.  Thanks for the tip.
> I will look into it; obviously, I would prefer the solution to
> be engine independent, but this feature might be more valuable :-)
>
> As usually, some good search engine (Google??? :D ) is your friend....

IMHO you have to always know which SQL engine is on the on the other side
(in other words you have to know how to set up the connection string).
If you know the engine, you can decide which kind of SQL "slang" to use:
http://www.petefreitag.com/item/466.cfm

Petr

Re: [SQLObject] Select Single Random Record

[Hans G. S. <geo...@sc...>]

On Wed, Apr 18, 2012 at 09:43:23PM +0200, Petr Jakeš wrote:
> > Although this might work in the particular application, but
> > it is hardly ideal to make two queries, nor to load a long list
> > of IDs.  Is there a way to do it with a single query?
> >
> > 1)
> Is your task really "time critical"?

In my case, yes; it is number crunching.
Question should be «is it /that/ "time critical"» :-)
I have had some difficulties with slow operations due
to multiple queries, and it feels more satisfactory get
rid of any avoidable query, even if the saving is only
a fraction of a percent of the total running time.

> How many records (IDs) do you expect to be returned using the first select?

thousands in current tests;
hundreds of thousands is likely in future tests,
and millions is plausible.

> How many kb will it take? Is the list size a real problem for your Internet
> connection?

Might be; especially when it is over the Internet as opposed to
over a LAN.  Yet, I am as concerned with query processing time than
transmission time.

> How often do you expect to release the select querry?

Could vary.  About 50 clients querying once a minute each
may be typical, but I am sure I will see faster jobs completing
in seconds, in which case each client would query correspondingly
often.

> 2)
> what is your target database engine?

postgres at the moment.

> some databases allow "rand" in the select query.
> see:
> http://stackoverflow.com/questions/19412/how-to-request-a-random-row-in-sql

Ah.  Thanks for the tip.
I will look into it; obviously, I would prefer the solution to
be engine independent, but this feature might be more valuable :-)

:-- George
> 
> Petr

-- 
:-- Hans Georg

Re: [SQLObject] Select Single Random Record

[Petr J. <pet...@tp...>]

> Although this might work in the particular application, but
> it is hardly ideal to make two queries, nor to load a long list
> of IDs.  Is there a way to do it with a single query?
>
> 1)
Is your task really "time critical"?
How many records (IDs) do you expect to be returned using the first select?
How many kb will it take? Is the list size a real problem for your Internet
connection?
How often do you expect to release the select querry?

2)
what is your target database engine?
some databases allow "rand" in the select query.
see:
http://stackoverflow.com/questions/19412/how-to-request-a-random-row-in-sql

Petr

Re: [SQLObject] Select Single Random Record

[Hans G. S. <geo...@sc...>]

On Wed, Apr 18, 2012 at 08:46:47PM +0200, Petr Jakeš wrote:
> *Get the list of valid IDs from the remote database using the raw SQL
> command
> something like:*
> 
> con = connectionForURI("firebird://yourUserName:yourPassword@serverAddress
> :3050/pat/to/database/database.file")
> 
> validIDs= "SELECT ID FROM SONGS_TABLE where ......"
> 
> returnedIDs = con.queryAll(validIDs)
> 
> # you get the list of valid IDs, something like this: [(1,), (2,), (3,),
> (4,), (5,), (6,), (7,), (8,), (9,), (11,)]
> 
> *than:*
> 
> import random
> randomID = random.choice(returnedIDs)[0]
> randomSong = SongsTable.get(randomID)

Although this might work in the particular application, but
it is hardly ideal to make two queries, nor to load a long list
of IDs.  Is there a way to do it with a single query?

-- 
:-- Hans Georg

Re: [SQLObject] Select Single Random Record

[Pʀoмᴇтнᴇυs 0. <pro...@gm...>]

I'll see about adding a recipe to the SQLObject Community Doc site for this.

(  https://sites.google.com/site/sqlobject/  )

On Wed, Apr 18, 2012 at 12:46 PM, Petr Jakeš <pet...@tp...> wrote:

>
> To give context to the issue, I am building my own icecast2 broadcaster. I
>> want
>> to have an Auto DJ feature which will pick a random song from the
>> database which
>> hasn't recently been played plus some other criteria. It really doesn't
>> matter
>> which record i get back from the database, I just need one at random.
>>
>
> *Get the list of valid IDs from the remote database using the raw SQL
> command
> something like:*
>
> con = connectionForURI("firebird://yourUserName:yourPassword@serverAddress
> :3050/pat/to/database/database.file")
>
> validIDs= "SELECT ID FROM SONGS_TABLE where ......"
>
> returnedIDs = con.queryAll(validIDs)
>
> # you get the list of valid IDs, something like this: [(1,), (2,), (3,),
> (4,), (5,), (6,), (7,), (8,), (9,), (11,)]
>
> *than:*
>
> import random
> randomID = random.choice(returnedIDs)[0]
> randomSong = SongsTable.get(randomID)
>
> HTH
>
> Regards
>
> Petr
>
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>
>

Re: [SQLObject] Select Single Random Record

[Petr J. <pet...@tp...>]

> To give context to the issue, I am building my own icecast2 broadcaster. I
> want
> to have an Auto DJ feature which will pick a random song from the database
> which
> hasn't recently been played plus some other criteria. It really doesn't
> matter
> which record i get back from the database, I just need one at random.
>

*Get the list of valid IDs from the remote database using the raw SQL
command
something like:*

con = connectionForURI("firebird://yourUserName:yourPassword@serverAddress
:3050/pat/to/database/database.file")

validIDs= "SELECT ID FROM SONGS_TABLE where ......"

returnedIDs = con.queryAll(validIDs)

# you get the list of valid IDs, something like this: [(1,), (2,), (3,),
(4,), (5,), (6,), (7,), (8,), (9,), (11,)]

*than:*

import random
randomID = random.choice(returnedIDs)[0]
randomSong = SongsTable.get(randomID)

HTH

Regards

Petr

Re: [SQLObject] Select Single Random Record

[Oleg B. <ph...@ph...>]

On Wed, Apr 18, 2012 at 05:18:41PM +0000, Adam Berg <ada...@gm...> wrote:
> Oleg Broytman <phd <at> phdru.name> writes:
> > On Wed, Apr 18, 2012 at 12:30:10PM -0400, Adam Berg <adamberg <at> gmail.com> 
> wrote:
> > > What is the best way to select a single random record from a table and
> > > falls within the "where" criteria i have defined? I don't want to return a
> > > huge result set each time and then pick a random one
> > 
> >    Please define "random" in the context of your task. Do you want a
> > different record every time? Or some non-deterministic record that could
> > be the same every time is a possible solution?
> 
> It should be a different record each time. 

   Do it in two steps. First, count the number of objects that satisfy
your criteria:

count = MyTable.select(whereClause).count()

   Optimize your whereClause and indices. Generate an int in range
0..count-1 (see module `random`). And select the item:

row = MyTable.select(whereClause, orderBy=MyTable.q.id)[random_int]

   With this query SQLObject uses OFFSET and LIMIT=1 to select exactly
that row.

> To give context to the issue, I am building my own icecast2 broadcaster. I want 
> to have an Auto DJ feature which will pick a random song from the database which 
> hasn't recently been played plus some other criteria. It really doesn't matter 
> which record i get back from the database, I just need one at random.

   Aha, you mark played songs in the DB, so your whereClause certainly
contains "if was not played yet" criteria. In this case selecting just
the first item without ordering the result set ought to be enough:

row = MyTable.select(whereClause)[0]

   You have to experiment.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Select Single Random Record

[Adam B. <ada...@gm...>]

Adam Berg <adamberg <at> gmail.com> writes:

> 
> Oleg Broytman <phd <at> phdru.name> writes:
> 
> > 
> > On Wed, Apr 18, 2012 at 12:30:10PM -0400, Adam Berg <adamberg <at> 
gmail.com> 
> wrote:
> > > What is the best way to select a single random record from a table and
> > > falls within the "where" criteria i have defined? I don't want to return a
> > > huge result set each time and then pick a random one
> > 
> >    Please define "random" in the context of your task. Do you want a
> > different record every time? Or some non-deterministic record that could
> > be the same every time is a possible solution?
> > 
> > Oleg.
> 
> It should be a different record each time. 
> I don't need a way to produce the same results again.
> 
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second 
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev

To give context to the issue, I am building my own icecast2 broadcaster. I want 
to have an Auto DJ feature which will pick a random song from the database which 
hasn't recently been played plus some other criteria. It really doesn't matter 
which record i get back from the database, I just need one at random.

Re: [SQLObject] Select Single Random Record

[Adam B. <ada...@gm...>]

Oleg Broytman <phd <at> phdru.name> writes:

> 
> On Wed, Apr 18, 2012 at 12:30:10PM -0400, Adam Berg <adamberg <at> gmail.com> 
wrote:
> > What is the best way to select a single random record from a table and
> > falls within the "where" criteria i have defined? I don't want to return a
> > huge result set each time and then pick a random one
> 
>    Please define "random" in the context of your task. Do you want a
> different record every time? Or some non-deterministic record that could
> be the same every time is a possible solution?
> 
> Oleg.

It should be a different record each time. 
I don't need a way to produce the same results again.

Re: [SQLObject] Select Single Random Record

[Hans G. S. <geo...@sc...>]

On Wed, Apr 18, 2012 at 08:38:42PM +0400, Oleg Broytman wrote:
> On Wed, Apr 18, 2012 at 12:30:10PM -0400, Adam Berg <ada...@gm...> wrote:
> > What is the best way to select a single random record from a table and
> > falls within the "where" criteria i have defined? I don't want to return a
> > huge result set each time and then pick a random one
> 
>    Please define "random" in the context of your task. Do you want a
> different record every time? Or some non-deterministic record that could
> be the same every time is a possible solution?

Obviously, i cannot defined «random» in his context, but I have
a somewhat related problem.

To me «random» means that every record is equally likely as
the return of the next execution of the query, where «likely»
can be entirely subjective seen from the user's point of view.

In my context the issue is a queue of number crunching jobs,
where a number of clients (10-100; maybe more) will query
for the next parameter set to run the calculation for.
A client receiving a job will set a field to indicate that
it is taken, and transaction locking is used to avoid 
multiple clients snitching the same job at the same time.

Ideally, I would have liked a query to retrieve the first
unlocked record (it is useful but not necessary to order
them by timestamp).

Random selection, which makes it unlikely that a client will
have to wait for the lock would be a useful second best. 

Or maybe there is another ingenious approach which I have not
thought of.  Admittedly, this is a quick and dirty solution
which seems to work.

-- 
:-- Hans Georg

Re: [SQLObject] Select Single Random Record

[Oleg B. <ph...@ph...>]

On Wed, Apr 18, 2012 at 12:30:10PM -0400, Adam Berg <ada...@gm...> wrote:
> What is the best way to select a single random record from a table and
> falls within the "where" criteria i have defined? I don't want to return a
> huge result set each time and then pick a random one

   Please define "random" in the context of your task. Do you want a
different record every time? Or some non-deterministic record that could
be the same every time is a possible solution?

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] Select Single Random Record

[Adam B. <ada...@gm...>]

What is the best way to select a single random record from a table and
falls within the "where" criteria i have defined? I don't want to return a
huge result set each time and then pick a random one, as the database is
located outside of my network and accessed over the internet.


-- 
Adam Berg

[SQLObject] connectionForURI is not defined

[Glenn R. <gru...@ed...>]

Everything was running fine last night.  Came in this morning and my 
test system is acting weird.  I'm doing my best to find the answer but 
in the meantime, if someone knows what this is, I could use a bit of help.

Thanks,

Glenn


Today:
 >>> from sqlobject import *
Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
   File "sqlobject.py", line 8, in <module>
     conn = connectionForURI(connection_string)
NameError: name 'connectionForURI' is not defined


System Setup:

Python 2.7.2 on Windows XP
Path = c:\python27;c:\python27\Scripts;C:\Python27\Lib\site-packages


Installed pymssql
Installed SQLObject 1.3.0




 >easy_install -U SQLObject
Searching for SQLObject
Reading http://pypi.python.org/simple/SQLObject/
Reading http://sqlobject.org
Reading http://sqlobject.org/
Reading http://sqlobject.org/devel/
Best match: SQLObject 1.3.0
Downloading 
http://pypi.python.org/packages/2.7/S/SQLObject/SQLObject-1.3.0-py2.7.egg#md5=42e649b0c1
08b75a1bec8f22e84270fa
Processing SQLObject-1.3.0-py2.7.egg
creating c:\python27\lib\site-packages\SQLObject-1.3.0-py2.7.egg
Extracting SQLObject-1.3.0-py2.7.egg to c:\python27\lib\site-packages
Adding SQLObject 1.3.0 to easy-install.pth file
Installing sqlobject-admin script to c:\python27\Scripts
Installing sqlobject-convertOldURI script to c:\python27\Scripts

Installed c:\python27\lib\site-packages\sqlobject-1.3.0-py2.7.egg
Processing dependencies for SQLObject
Finished processing dependencies for SQLObject

[SQLObject] connectionForURI is not defined

[Glenn R. <gru...@ed...>]

Nevermind.

I would share with you the reason, but I don't want to get banned from 
The Internet.  And yes.  I mean 'The Whole Internet'.

-Glenn

Re: [SQLObject] SQLObject 1.3.0

[Oleg B. <ph...@ph...>]

On Sat, Mar 31, 2012 at 03:42:38PM +0400, Oleg Broytman wrote:
> I'm pleased to announce version 1.3.0, the first stable release of branch
> 1.3 of SQLObject.

   With this release I stopped supporting branch 1.1.

> * Major update of FirebirdConnection: introspection was completely
>   rewritten and extended; ``charset`` was renamed to ``dbEncoding``;
>   a longstanding bug was fixed - pass port to connect().

   Many kudos to Petr Jakes!

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.