sqlobject-discuss — All things SQLObject-related

Re: [SQLObject] PATCH: adds support for an interval timedelta column

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

On Fri, May 15, 2009 at 10:09:01AM -0700, Daniel Fetchinson wrote:
> Actually, I think TimedeltaCol could be implemented for sqlite as
> well. Although it doesn't have an INTERVAL data type it could use a
> plain TEXT instead and python would do the conversion. As far as I
> know sqlite only knows TEXT anyway so IntCol, StringCol, etc, all
> these things are implemented as TEXT and the data conversion is done
> by python. The TimedeltaCol could be similar.

   Well, not exactly - SQLite understands and produces some data types -
pysqlite passes them unmodified AFAIU. But anyway I did a similar trick
with DecimalStringCol - it stores decimals as strings to work around
SQLite's "type affinity" feature.

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] PATCH: adds support for an interval timedelta column

[Daniel F. <fet...@go...>]

>> Here's another test, added to the bottom of test_converters.py:
>
>    Thanks!
>
>> By the way, how do I write a converter that converts a python object one
>> way for one database (sqlite) and another way for another database
>> (postgres)?  Are there any examples of this already?
>
>    Yes, see StringLikeConverter.

Actually, I think TimedeltaCol could be implemented for sqlite as
well. Although it doesn't have an INTERVAL data type it could use a
plain TEXT instead and python would do the conversion. As far as I
know sqlite only knows TEXT anyway so IntCol, StringCol, etc, all
these things are implemented as TEXT and the data conversion is done
by python. The TimedeltaCol could be similar.

Cheers,
Daniel


-- 
Psss, psss, put it down! - http://www.cafepress.com/putitdown

Re: [SQLObject] Running test_auto.py causes segfault

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

On Thu, May 14, 2009 at 02:53:57PM +0000, Matthew Wilson wrote:
> The test_dynamicJoin method in sqlobject/tests/test_auto.py causes a segfault for me:
> 
>     $ py.test --verbose test_auto.py
>     python: platform linux2 -- Python 2.5.2 -- /home/matt/virtualenvs/scratch/bin/python
>     using py lib: /home/matt/virtualenvs/scratch/lib/python2.5/site-packages/py-1.0.0b1-py2.5.egg/py <rev unknown>
>     test object 1: /home/matt/checkouts/SQLObject/sqlobject/tests/test_auto.py
> 
>     /home/matt/svn-checkouts/SQLObject/sqlobject/tests/test_auto.py:36: TestPeople.test_defaultOrder PASS
>     /home/matt/svn-checkouts/SQLObject/sqlobject/tests/test_auto.py:40: TestPeople.test_dynamicColumn PASS
>     /home/matt/svn-checkouts/SQLObject/sqlobject/tests/test_auto.py:48: TestPeople.test_dynamicJoin Segmentation fault
> 
> Anyone else seeing this problem?

   Works for me:

============================= test session starts ==============================
python: platform linux2 -- Python 2.5.2 -- /usr/bin/python
using py lib: /usr/local/src/Python/py-dist/py <rev 65166>
test object 1:
/home/phd/work/SQLObject/SQLObject-trunk/sqlobject/tests/test_auto.py

test_auto.py:36: TestPeople.test_defaultOrder PASS
test_auto.py:40: TestPeople.test_dynamicColumn PASS
test_auto.py:48: TestPeople.test_dynamicJoin PASS
test_auto.py:68: TestPeople.test_collidingName PASS
test_auto.py:170: TestAuto.test_classCreate PASS

=========================== 5 passed in 0.67 seconds ===========================

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] Running test_auto.py causes segfault

[Matthew W. <ma...@tp...>]

The test_dynamicJoin method in sqlobject/tests/test_auto.py causes a segfault for me:

    $ py.test --verbose test_auto.py
    python: platform linux2 -- Python 2.5.2 -- /home/matt/virtualenvs/scratch/bin/python
    using py lib: /home/matt/virtualenvs/scratch/lib/python2.5/site-packages/py-1.0.0b1-py2.5.egg/py <rev unknown>
    test object 1: /home/matt/checkouts/SQLObject/sqlobject/tests/test_auto.py

    /home/matt/svn-checkouts/SQLObject/sqlobject/tests/test_auto.py:36: TestPeople.test_defaultOrder PASS
    /home/matt/svn-checkouts/SQLObject/sqlobject/tests/test_auto.py:40: TestPeople.test_dynamicColumn PASS
    /home/matt/svn-checkouts/SQLObject/sqlobject/tests/test_auto.py:48: TestPeople.test_dynamicJoin Segmentation fault

Anyone else seeing this problem?

Re: [SQLObject] PATCH: adds support for an interval timedelta column

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

On Thu, May 14, 2009 at 02:32:31PM +0000, Matthew Wilson wrote:
> Here's another test, added to the bottom of test_converters.py:

   Thanks!

> By the way, how do I write a converter that converts a python object one
> way for one database (sqlite) and another way for another database
> (postgres)?  Are there any examples of this already?

   Yes, see StringLikeConverter.

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] PATCH: adds support for an interval timedelta column

[Matthew W. <ma...@tp...>]

On Thu 14 May 2009 10:18:47 AM EDT, Matthew Wilson wrote:
> On Wed 13 May 2009 04:35:59 PM EDT, Oleg Broytmann wrote:
>> On Wed, May 13, 2009 at 08:05:26PM +0000, Matthew Wilson wrote:
>>> >    IWBN to have a test also.
>>> 
>>> I completely agree; can you point me to where in the code I should write
>>> the test?  Also, are there any tests I can use as a guide?
>>
>>    Any test script would be ok - I'll convert it to the test suit myself.
>> But of course a test in SQLObject style would be even better.
>>    SQLObject uses py.test as its testing environment. You can find a lot of
>> tests in sqlobject/tests/ directory.

Here's another test, added to the bottom of test_converters.py:

    $ svn diff test_converters.py
    Index: test_converters.py
    ===================================================================
    --- test_converters.py  (revision 3881)
    +++ test_converters.py  (working copy)
    @@ -1,4 +1,5 @@
     import sys
    +from datetime import timedelta
     from sqlobject.sqlbuilder import sqlrepr
     from sqlobject.sqlbuilder import SQLExpression, SQLObjectField, \
          Select, Insert, Update, Delete, Replace, \
    @@ -195,3 +196,8 @@
                 pass
             else:
                 assert sqlrepr(Set([1])) == "(1)"
    +
    +def test_timedeltas():
    +
    +    assert sqlrepr(timedelta(seconds=30*60)) == \
    +    "INTERVAL '0 days 1800 seconds'"

By the way, how do I write a converter that converts a python object one
way for one database (sqlite) and another way for another database
(postgres)?  Are there any examples of this already?

Re: [SQLObject] PATCH: adds support for an interval timedelta column

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

On Thu, May 14, 2009 at 02:18:47PM +0000, Matthew Wilson wrote:
> I'm trying to write a test, but it seems like all the tests use a sqlite
> database, and sqlite doesn't support an interval datatype.
> 
> Not sure what to do at this point.  Here's the test (absolutely
> nothing fancy here):
> 
>     $ cat test_interval.py
>     # vim: set expandtab ts=4 sw=4 filetype=python:
> 
>     from datetime import timedelta
> 
>     from sqlobject import *
>     from sqlobject.tests.dbtest import *
> 
>     class Student(SQLObject):
>         break_time = TimedeltaCol()
> 
>     def test_timedeltaCol():
>         setupClass(Student)
>         td = timedelta(seconds=60*60)
>         student = Student(break_time=td)
>         assert student.break_time == td
> 
> When I run py.test test_interval.py, I get an operational error that
> comes from sqlite rejecting the interval syntax.
> 
> Ideas?  Should I create a postgresql database in my setup method and
> then connect to that for my test?

   It should be something like

$ createdb test
$ py.test test_interval.py -D postgres:/test
$ dropdb test

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] PATCH: adds support for an interval timedelta column

[Matthew W. <ma...@tp...>]

On Wed 13 May 2009 04:35:59 PM EDT, Oleg Broytmann wrote:
> On Wed, May 13, 2009 at 08:05:26PM +0000, Matthew Wilson wrote:
>> >    IWBN to have a test also.
>> 
>> I completely agree; can you point me to where in the code I should write
>> the test?  Also, are there any tests I can use as a guide?
>
>    Any test script would be ok - I'll convert it to the test suit myself.
> But of course a test in SQLObject style would be even better.
>    SQLObject uses py.test as its testing environment. You can find a lot of
> tests in sqlobject/tests/ directory.


I'm trying to write a test, but it seems like all the tests use a sqlite
database, and sqlite doesn't support an interval datatype.

Not sure what to do at this point.  Here's the test (absolutely
nothing fancy here):

    $ cat test_interval.py
    # vim: set expandtab ts=4 sw=4 filetype=python:

    from datetime import timedelta

    from sqlobject import *
    from sqlobject.tests.dbtest import *

    class Student(SQLObject):
        break_time = TimedeltaCol()

    def test_timedeltaCol():
        setupClass(Student)
        td = timedelta(seconds=60*60)
        student = Student(break_time=td)
        assert student.break_time == td

When I run py.test test_interval.py, I get an operational error that
comes from sqlite rejecting the interval syntax.

Ideas?  Should I create a postgresql database in my setup method and
then connect to that for my test?

Re: [SQLObject] PATCH: adds support for an interval timedelta column

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

On Wed, May 13, 2009 at 08:05:26PM +0000, Matthew Wilson wrote:
> >    IWBN to have a test also.
> 
> I completely agree; can you point me to where in the code I should write
> the test?  Also, are there any tests I can use as a guide?

   Any test script would be ok - I'll convert it to the test suit myself.
But of course a test in SQLObject style would be even better.
   SQLObject uses py.test as its testing environment. You can find a lot of
tests in sqlobject/tests/ directory.

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] PATCH: adds support for an interval timedelta column

[Matthew W. <ma...@tp...>]

On Wed 13 May 2009 03:39:01 PM EDT, Oleg Broytmann wrote:
> On Wed, May 13, 2009 at 07:11:22PM +0000, Matthew Wilson wrote:
>> Hi -- I wrote some code to add a TimedeltaCol type.  I only tested it in
>> postgresql.
>
>    Thank you!
>
>> +def TimedeltaConverter(value, db):
>> +    
>> +    return """INTERVAL '%d days %d seconds'""" % \
>> +        (value.days, value.seconds)
>> +
>> +registerConverter(datetime.timedelta, TimedeltaConverter)
>
>    The syntax is only valid in Postgres, so it has to be protected:
>
> def TimedeltaConverter(value, db):
>     if db == 'postgres':
>         return """INTERVAL '%d days %d seconds'""" % \
>             (value.days, value.seconds)
>     else:
>         raise ValueError('TimedeltaCol is only implemented for Postgres')
>
>> +class TimedeltaValidator(validators.Validator):
>> +    def to_python(self, value, state):
>> +        return value
>> +
>> +    def from_python(self, value, state):
>> +        return value
>
>    Why empty validator?
>
>    IWBN to have a test also.

I completely agree; can you point me to where in the code I should write
the test?  Also, are there any tests I can use as a guide?

Later this week, I'll try to send in an updated patch with the code you
added and a test.

Matt

Re: [SQLObject] PATCH: adds support for an interval timedelta column

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

On Wed, May 13, 2009 at 07:11:22PM +0000, Matthew Wilson wrote:
> Hi -- I wrote some code to add a TimedeltaCol type.  I only tested it in
> postgresql.

   Thank you!

> +def TimedeltaConverter(value, db):
> +    
> +    return """INTERVAL '%d days %d seconds'""" % \
> +        (value.days, value.seconds)
> +
> +registerConverter(datetime.timedelta, TimedeltaConverter)

   The syntax is only valid in Postgres, so it has to be protected:

def TimedeltaConverter(value, db):
    if db == 'postgres':
        return """INTERVAL '%d days %d seconds'""" % \
            (value.days, value.seconds)
    else:
        raise ValueError('TimedeltaCol is only implemented for Postgres')

> +class TimedeltaValidator(validators.Validator):
> +    def to_python(self, value, state):
> +        return value
> +
> +    def from_python(self, value, state):
> +        return value

   Why empty validator?

   IWBN to have a test also.

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] PATCH: adds support for an interval timedelta column

[Matthew W. <ma...@tp...>]

Hi -- I wrote some code to add a TimedeltaCol type.  I only tested it in
postgresql.

I'll improve this code if you tell me what I should do.  I find the
SQLOjbect internals confusing.


Matt

Index: converters.py
===================================================================
--- converters.py	(revision 3881)
+++ converters.py	(working copy)
 
@@ -187,6 +187,14 @@
 
 registerConverter(Decimal, DecimalConverter)
 
+def TimedeltaConverter(value, db):
+    
+    return """INTERVAL '%d days %d seconds'""" % \
+        (value.days, value.seconds)
+
+registerConverter(datetime.timedelta, TimedeltaConverter)
+        
+
 def sqlrepr(obj, db=None):
     try:
         reprFunc = obj.__sqlrepr__
Index: col.py
===================================================================
--- col.py	(revision 3881)
+++ col.py	(working copy)
@@ -1517,6 +1517,32 @@
     baseClass = SOPickleCol
 
 
+class TimedeltaValidator(validators.Validator):
+
+    def to_python(self, value, state):
+        return value
+
+    def from_python(self, value, state):
+        return value
+
+
+class SOTimedeltaCol(SOCol):
+
+    def _postgresType(self):
+        return 'INTERVAL'
+
+    def createValidators(self):
+        return [TimedeltaValidator(name=self.name)] + \
+            super(SOTimedeltaCol, self).createValidators()
+
+    
+
+class TimedeltaCol(Col):
+    baseClass = SOTimedeltaCol
+
+
+
+
 def pushKey(kw, name, value):
     if not kw.has_key(name):
         kw[name] = value

Re: [SQLObject] Joins with aliasing

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

On Tue, May 12, 2009 at 07:47:10PM -0400, Andrew Peace wrote:
> class Item(SQLObject):
>     """An item definition (e.g. 'The Life of Brian DVD')"""
>     name            = StringCol(length=15, alternateID=True)
>     attributes      = MultipleJoin('ItemAttribute')
> 
> class Attribute(SQLObject):
>     """An attribute definition (e.g. ISBN is a String)"""
>     #columns
>     name     = StringCol(length=10, alternateID=True)
>     title    = StringCol(length=20)
>     dataType = IntCol(length=1)
> 
> class ItemAttribute(SQLObject):
>     """An attribute instantiation (e.g. ISBN='abcd1234')"""
>     item      = ForeignKey('Item', cascade=True)
>     attribute = ForeignKey('Attribute')
>     value     = StringCol(length=50)
> 
> SELECT item.*
> FROM item
> LEFT JOIN item_attribute as item_attribute0 ON item.id = item_attribute0.item_id
> LEFT JOIN attribute as attribute0 on attribute0.id =
> item_attribute0.attribute_id
> LEFT JOIN item_attribute as item_attribute1 ON item_attribute0.item_id
> = item_attribute1.item_id
> LEFT JOIN attribute as attribute1 on attribute1.id =
> item_attribute1.attribute_id
> WHERE 1
> AND   attribute0.name = 'price'
> AND   item_attribute0.value = '19.99'
> AND   attribute1.name = 'isbn'
> AND   item_attribute1.value = 'life123';

from sqlobject.sqlbuilder import Alias, LEFTJOINOn

attribute0 = Alias(Attribute, 'attribute0')
item_attribute0 = Alias(ItemAttribute, 'item_attribute0')
item_attribute1 = Alias(ItemAttribute, 'item_attribute1')

   and then something like this:

Item.select(
   join=[
      LEFTJOINOn(None, item_attribute0, Item.q.id == item_attribute0.q.itemID),
      LEFTJOINOn(None, attribute0, attribute0.q.id == item_attribute0.q.attributeID),
         ... other left joins ...
   ],
   clause = (
      (attribute0.q.name == 'price') &&
      (item_attribute0.q.value == 19.99) &&
         ... other where clauses ...
   )
)

   Or, if you prefer this form

   clause = AND(
      (attribute0.q.name == 'price'),
      (item_attribute0.q.value == 19.99),
         ... other where clauses ...
   )

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] Joins with aliasing

[Andrew P. <ap...@gm...>]

I have quite a complex query, and I am trying to select from the
database with SQLObject instead of using the query directly. Here is
the table structure:

class Item(SQLObject):
    """An item definition (e.g. 'The Life of Brian DVD')"""
    name            = StringCol(length=15, alternateID=True)
    attributes      = MultipleJoin('ItemAttribute')

class Attribute(SQLObject):
    """An attribute definition (e.g. ISBN is a String)"""
    #columns
    name     = StringCol(length=10, alternateID=True)
    title    = StringCol(length=20)
    dataType = IntCol(length=1)

class ItemAttribute(SQLObject):
    """An attribute instantiation (e.g. ISBN='abcd1234')"""
    item      = ForeignKey('Item', cascade=True)
    attribute = ForeignKey('Attribute')
    value     = StringCol(length=50)

As you can see, each item may have zero or more item_attributes. Each
item_attribute relates to exactly one attribute, which gives it an
attribute name.

Here is my query:

SELECT item.*
FROM item
LEFT JOIN item_attribute as item_attribute0 ON item.id = item_attribute0.item_id
LEFT JOIN attribute as attribute0 on attribute0.id =
item_attribute0.attribute_id
LEFT JOIN item_attribute as item_attribute1 ON item_attribute0.item_id
= item_attribute1.item_id
LEFT JOIN attribute as attribute1 on attribute1.id =
item_attribute1.attribute_id
WHERE 1
AND   attribute0.name = 'price'
AND   item_attribute0.value = '19.99'
AND   attribute1.name = 'isbn'
AND   item_attribute1.value = 'life123';

In this specific example, the query (in MySQL) selects all items that
have a price of 19.99 and ISBN of 'life123'.

More generally, I use queries like this to select items that have
certain attributes. Each attribute I am searching for creates two left
joins, one for the item_attribute itself and one for the attribute's
name.

Not sure how to make such a selection through the SQLObject ORM. Any
help is greatly appreciated!

-Andrew Peace

Re: [SQLObject] help with circular foreign keys?

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

On Tue, May 12, 2009 at 02:57:38PM -0400, inhahe wrote:
> On Tue, May 12, 2009 at 4:00 AM, Oleg Broytmann <ph...@ph...> wrote:
> > On Tue, May 12, 2009 at 03:08:16AM -0400, inhahe wrote:
> > > try:
> > >   Pics.createTable()
> > >   print "Created table Pics"
> > > except dberrors.OperationalError: pass
> >
> >    Why do you need these try/except?
> 
> i want it to create each table but only if the table doesn't already exist

Pics.createTable(ifNotExists=True)

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] help with circular foreign keys?

[inhahe <in...@gm...>]

On Tue, May 12, 2009 at 4:00 AM, Oleg Broytmann <ph...@ph...> wrote:

> On Tue, May 12, 2009 at 03:08:16AM -0400, inhahe wrote:
> > class Pics(SQLObject):
> >   itemid = IntCol()
> >   picdata = BLOBCol()
> >   thumbnail = ForeignKey("Thumbs", cascade='null')
> > try:
> >   Pics.createTable()
> >   print "Created table Pics"
> > except dberrors.OperationalError: pass
>
>    Why do you need these try/except?


i want it to create each table but only if the table doesn't already exist
if it already exists it gives me an operationalerror.
i had tried looking for a better way but couldn't find one!


>
> http://sqlobject.org/FAQ.html#mutually-referencing-tables
>
>
ah, thanks

Re: [SQLObject] help with circular foreign keys?

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

On Tue, May 12, 2009 at 03:08:16AM -0400, inhahe wrote:
> class Pics(SQLObject):
>   itemid = IntCol()
>   picdata = BLOBCol()
>   thumbnail = ForeignKey("Thumbs", cascade='null')
> try:
>   Pics.createTable()
>   print "Created table Pics"
> except dberrors.OperationalError: pass

   Why do you need these try/except?

> class Thumbs(SQLObject):
>   itemid = IntCol()
>   pic = ForeignKey("Pics", cascade=True)
>   picdata = BLOBCol()
> try:
>   Pics.createTable()
>   print "Created table Pics"
> except dberrors.OperationalError: pass
> 
> KeyError: 'No class Thumbs found in the registry

http://sqlobject.org/FAQ.html#mutually-referencing-tables

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] help with circular foreign keys?

[inhahe <in...@gm...>]

sorry if there was something in the documentation i should have understood,
but i'm having this problem

the code:

class Pics(SQLObject):
  itemid = IntCol()
  picdata = BLOBCol()
  thumbnail = ForeignKey("Thumbs", cascade='null')
try:
  Pics.createTable()
  print "Created table Pics"
except dberrors.OperationalError: pass

class Thumbs(SQLObject):
  itemid = IntCol()
  pic = ForeignKey("Pics", cascade=True)
  picdata = BLOBCol()
try:
  Pics.createTable()
  print "Created table Pics"
except dberrors.OperationalError: pass

the error:

KeyError: 'No class Thumbs found in the registry [default] (these classes
exist:
 Log, Pics, RegisterSessions, SQLObject, Sessions, Users)'

that list is a list of all the tables created before i got to that point, so
i assume the error is that Thumbs must be registered before I can make a
foreign key to it, but then if I put Thumbs before Pics, Pics wouldn't be
registered yet when I try to make a foreign key to that.  how do i solve
this?  sorry if the answer is supposed to be obvious =p

Re: [SQLObject] SQLObject is alive!

[Daniel F. <fet...@go...>]

>> > Hello! I am going to do the next round of minor releases. Does anybody
>> > need
>> > a beta period?
>>
>> Oooops, I missed this announcement. In general I don't need a beta
>> period at all, since if the new versions are not okay, I can simply
>> switch back to the older version.
>
>    I usually don't make betas for minor releases but this time there were
> many changes (albeit minor ones) in a long period without release.

Makes perfect sense.
In any case it's good to see that sqlobject is alive!

Cheers,
Daniel


-- 
Psss, psss, put it down! - http://www.cafepress.com/putitdown

Re: [SQLObject] SQLObject is alive!

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

On Mon, May 11, 2009 at 10:30:56AM -0700, Daniel Fetchinson wrote:
> > Hello! I am going to do the next round of minor releases. Does anybody need
> > a beta period?
> 
> Oooops, I missed this announcement. In general I don't need a beta
> period at all, since if the new versions are not okay, I can simply
> switch back to the older version.

   I usually don't make betas for minor releases but this time there were
many changes (albeit minor ones) in a long period without release.

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] SQLObject is alive!

[Daniel F. <fet...@go...>]

> Hello! I am going to do the next round of minor releases. Does anybody need
> a beta period?

Oooops, I missed this announcement. In general I don't need a beta
period at all, since if the new versions are not okay, I can simply
switch back to the older version.

The new 0.10.5 version works perfectly with my app, thanks for the hard work!

Cheers,
Danil

-- 
Psss, psss, put it down! - http://www.cafepress.com/putitdown

Re: [SQLObject] Python 2.6

[Daniel F. <fet...@go...>]

> Since revision 3880 SQLObject works with Python 2.6; actually, it worked
> just fine even before but it raised a DeprecationWarning on import sets;
> now it doesn't and is fully tested with SQLite and Postgres. On the next
> releases (0.10.6 and 0.11) there will be python eggs for 2.6.

This is great, thanks a lot, Oleg!

Cheers,
Daniel

-- 
Psss, psss, put it down! - http://www.cafepress.com/putitdown

[SQLObject] Python 2.6

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

Since revision 3880 SQLObject works with Python 2.6; actually, it worked
just fine even before but it raised a DeprecationWarning on import sets;
now it doesn't and is fully tested with SQLite and Postgres. On the next
releases (0.10.6 and 0.11) there will be python eggs for 2.6.

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] SQLObject 0.10.5

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

Hello!

I'm pleased to announce version 0.10.5, a minor bugfix release of 0.10 branch
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://cheeseshop.python.org/pypi/SQLObject/0.10.5

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


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

News since 0.10.4
-----------------

* Another unicode-related patch for MySQL; required because different
  versions of MySQLdb require different handling::

   - MySQLdb < 1.2.1: only ascii
   - MySQLdb = 1.2.1: only unicode
   - MySQLdb > 1.2.1: both ascii and unicode

* Setup requires FormEncode version 1.1.1+.

* Fixed a minor bug - pass name to DecimalValidator.

* Fixed a bug in InheritableIteration - pass connection to child
  klass.select().

* sqlmeta.getColumns() becomes classmethod.

* A bug was fixed in PostgresConnection.columnsFromSchema() - foreign keys
  are now recognized and created as proper ForeignKey with correct
  column name and table name.

* Bugs in PostgresConnection and MSSQLConnection related to properties was
  fixed. A note for developers: from now on properties in DBConnection
  classes are forbidden as they don't work with Transaction -
  Transaction.__getattr__() cannot properly wrap 'self' so a property is
  called with wrong 'self'.

* Transaction instances now explicitly raises TypeError on close() -
  without this calling Transaction.close() calls connection.close() which
  is wrong.

* A bug in SQLiteConnection.columnsFromSchema() that led to an infinite
  loop was fixed.

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

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] SQLObject 0.9.10

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

Hello!

I'm pleased to announce version 0.9.10, a minor bugfix release of 0.9 branch
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://cheeseshop.python.org/pypi/SQLObject/0.9.10

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


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

News since 0.9.9
----------------

* Another unicode-related patch for MySQL; required because different
  versions of MySQLdb require different handling::

   - MySQLdb < 1.2.1: only ascii
   - MySQLdb = 1.2.1: only unicode
   - MySQLdb > 1.2.1: both ascii and unicode

* Setup requires FormEncode version 1.1.1+.

* Fixed a minor bug - pass name to DecimalValidator.

* Fixed a bug in InheritableIteration - pass connection to child
  klass.select().

* A bug was fixed in PostgresConnection.columnsFromSchema() - foreign keys
  are now recognized and created as proper ForeignKey with correct
  column name and table name.

* Bugs in PostgresConnection and MSSQLConnection related to properties was
  fixed. A note for developers: from now on properties in DBConnection
  classes are forbidden as they don't work with Transaction -
  Transaction.__getattr__() cannot properly wrap 'self' so a property is
  called with wrong 'self'.

* Transaction instances now explicitly raises TypeError on close() -
  without this calling Transaction.close() calls connection.close() which
  is wrong.

* A bug in SQLiteConnection.columnsFromSchema() that led to an infinite
  loop was fixed.

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

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.