headers
Oleg Broytmann | 1 Oct 2007 17:37
X-Face
Picon
Favicon

SQLObject 0.7.9b1

Hello!

I'm pleased to announce the 0.7.9b1, the first beta of 0.7.9 release 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, and
Firebird.  It also has newly added support for Sybase, MSSQL and MaxDB (also
known as SAPDB).

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

Site:
http://sqlobject.org

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.7.9b1
(Continue reading)

Permalink | Reply | 0 comments |
headers
Oleg Broytmann | 1 Oct 2007 17:44
X-Face
Picon
Favicon

SQLObject 0.8.6b1

Hello!

I'm pleased to announce the 0.8.6b1, the first beta of 0.8.6 release 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, and
Firebird.  It also has newly added support for 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
(Continue reading)

Permalink | Reply | 0 comments |
headers
Oleg Broytmann | 1 Oct 2007 17:49
X-Face
Picon
Favicon

SQLObject 0.9.2b1

Hello!

I'm pleased to announce the 0.9.2b1, the first beta of 0.9.2 release 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, and
Firebird.  It also has newly added support for 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
(Continue reading)

Permalink | Reply | 47 comments |
headers
Markus Gritsch | 2 Oct 2007 09:34
Picon

Re: SQLObject 0.9.2b1

Hi,

the new version 0.9.2b1 added a try except block around the conversion
to unicode of the query in mysqlconnection.py:

    if self.need_unicode and not isinstance(query, unicode):
        try:
            query = unicode(query, self.encoding)
        except UnicodeError:
            pass

In which case is it necessary that the UnicodeError is silently
ignored?  Isn't it dangerous and misleading to swallow such an
exception?

Kind regards,
Markus

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
Permalink | Reply | 46 comments |
headers
Oleg Broytmann | 2 Oct 2007 19:20
X-Face
Picon
Favicon

Re: SQLObject 0.9.2b1

Hello!

On Tue, Oct 02, 2007 at 09:34:08AM +0200, Markus Gritsch wrote:
> the new version 0.9.2b1 added a try except block around the conversion
> to unicode of the query in mysqlconnection.py:
> 
>     if self.need_unicode and not isinstance(query, unicode):
>         try:
>             query = unicode(query, self.encoding)
>         except UnicodeError:
>             pass
> 
> In which case is it necessary that the UnicodeError is silently
> ignored?  Isn't it dangerous and misleading to swallow such an
> exception?

   Pretty valid concern that deserves a longer answer.

   From time to time people report problems with MySQLdb and unicode. See
this report, for example:

http://sourceforge.net/mailarchive/forum.php?thread_name=54b165660707111303h45521239ncc4df928fb40a975%40mail.gmail.com&forum_name=sqlobject-discuss

   I never knew how to fix the problem, and was reluctant to apply
different patches that were more like small hacks to fix small part of
the problem.
   Finally David Turner dived into the problem and, using test_blob.py and
test_unicode.py tests, fixed the problem; the try/except is the part of the
solution.
   As I don't use MySQL I have to rely on the work of other people, and
(Continue reading)

Permalink | Reply | 45 comments |
headers
Markus Gritsch | 3 Oct 2007 08:32
Picon

Re: SQLObject 0.9.2b1

On 10/2/07, Oleg Broytmann <phd <at> phd.pp.ru> wrote:

>    Do you have a problem with the new code?

No, so far it works fine.

Markus

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
Permalink | Reply | 0 comments |
headers
Andres Freund | 3 Oct 2007 11:22
Picon

Re: SQLObject 0.9.2b1

Hi,

On Tuesday 02 October 2007, Oleg Broytmann wrote in "Re: [SQLObject] SQLObject 
0.9.2b1":
> Hello!
>
> On Tue, Oct 02, 2007 at 09:34:08AM +0200, Markus Gritsch wrote:
> > the new version 0.9.2b1 added a try except block around the conversion
> > to unicode of the query in mysqlconnection.py:
> >
> >     if self.need_unicode and not isinstance(query, unicode):
> >         try:
> >             query = unicode(query, self.encoding)
> >         except UnicodeError:
> >             pass
> >
> > In which case is it necessary that the UnicodeError is silently
> > ignored?  Isn't it dangerous and misleading to swallow such an
> > exception?
>
>    Pretty valid concern that deserves a longer answer.
>
>    From time to time people report problems with MySQLdb and unicode. See
> this report, for example:
> ...
>    I never knew how to fix the problem, and was reluctant to apply
> different patches that were more like small hacks to fix small part of
> the problem.
>    Finally David Turner dived into the problem and, using test_blob.py and
> test_unicode.py tests, fixed the problem; the try/except is the part of the
(Continue reading)

Permalink | Reply | 43 comments |
headers
Daniel Nogradi | 3 Oct 2007 20:59
Picon

ticket/294

I was wondering what the forseeable future of
http://sqlobject.gcu.info/trac/ticket/294 is. Are there plans to fix
this bug or is the general approach is that inheriable sqlobjects
should only be used in simple cases? It would be great to know because
I need to design my model accordingly.

Cheers,
Daniel

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
Permalink | Reply | 1 comment |
headers
Oleg Broytmann | 3 Oct 2007 21:12
X-Face
Picon
Favicon

Re: ticket/294

On Wed, Oct 03, 2007 at 08:59:27PM +0200, Daniel Nogradi wrote:
> http://sqlobject.gcu.info/trac/ticket/294

   If you replace the first join with (replace None with animal table)
joins.append( LEFTJOINOn( animal, cage, animal.q.cageID==cage.q.id ) )
   would it help?

Oleg.
--

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

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
Permalink | Reply | 0 comments |
headers
David Turner | 3 Oct 2007 22:46
Gravatar

Re: SQLObject 0.9.2b1

On Wed, 2007-10-03 at 11:22 +0200, Andres Freund wrote:
> Hi,
> 
> On Tuesday 02 October 2007, Oleg Broytmann wrote in "Re: [SQLObject] SQLObject 
> 0.9.2b1":
> > Hello!
> >
> > On Tue, Oct 02, 2007 at 09:34:08AM +0200, Markus Gritsch wrote:
> > > the new version 0.9.2b1 added a try except block around the conversion
> > > to unicode of the query in mysqlconnection.py:
> > >
> > >     if self.need_unicode and not isinstance(query, unicode):
> > >         try:
> > >             query = unicode(query, self.encoding)
> > >         except UnicodeError:
> > >             pass
> >    Finally David Turner dived into the problem and, using test_blob.py and
> > test_unicode.py tests, fixed the problem; the try/except is the part of the
> > solution.
> Perhaps it would be nice to include that description or the one of David in a 
> comment? Those statements surely raise a warning light in the head of many 
> people...

I was thinking that it might make more sense to just remove that whole
section.  I understand that whoever wrote that code thought it was
necessary to convert to Unicode, but I think it is not.  Can you comment
on this idea?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
(Continue reading)

Permalink | Reply | 42 comments |

Gmane