sqlobject-discuss — All things SQLObject-related

Re: [SQLObject] Table locking with MySQL

[Jason H. <jas...@gm...>]

On 30 November 2010 17:47, Oleg Broytman <ph...@ph...> wrote:
>   You can use low-level API like connection.query('LOCK...'). But I think
> a better way would be to insert an AssemblyResult row in advance, use its
> generated id (databases guarantee uniqueness and monotony of generated
> id's) to create a document and then update the row with the name of the
> document:

This is (sort of) the approach I have now, but it won't work for
indexing results for individual assemblies (which is what I want to
move to), eg:

>    row = AssemblyResult(doc, ...)
>    number = row.id

Even if this result is the first for a particular assembly, "number"
will be something in the tens-of-thousands, instead of just 1. So
maybe the low level API is the way to go.

Cheers,
Jason

Re: [SQLObject] Table locking with MySQL

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

On Tue, Nov 30, 2010 at 10:18:58AM +0800, Jason Heeris wrote:
> I am using SQLObject (0.12.4, but could be later) with MySQL 5.1 as
> the storage for a CherryPy based web app. I have a table "assembly"
> which refers to another table "assembly_results"; the SQLObject class
> def is something like:
> 
>     class Assembly(SQLObject):
>         dbAssemblyResults = MultipleJoin('AssemblyResult',
> joinColumn='db_assembly_id')
>         ...
> 
>     class AssemblyResult(SQLObject):
>         dbAssembly = ForeignKey('Assembly')
>         ...
> 
> Both tables are InnoDB.
> 
> To upload new results, I need to generate a filename that includes an
> index of the file, eg. the 5th result uploaded against an assembly is
> named "05. Some file...".  So I have the following:
> 
>     # asmbly is an instance of Assembly
>     number = len(asmbly.dbAssemblyResults) + 1
>     new_name = construct_name(number, ...)
>     doc = create_document(new_name, ...)
>     # create_document returns an instance of another SQLObject subclass
>     AssemblyResult(doc, ...)
> 
> The trouble is that there's a race hazard here ??? two uploads at almost
> the same time will see the same number of uploaded documents and I'll
> end up with two file names with the same index.
> 
> The simplest way I could think of to make this safe is to lock the
> assembly_result table for the duration of these calls (not
> unreasonable in my situation), but I can't find support for table
> locking in the SQLObject docs. Is it there, or should I use raw SQL
> calls? Or is there a better way?

   You can use low-level API like connection.query('LOCK...'). But I think
a better way would be to insert an AssemblyResult row in advance, use its
generated id (databases guarantee uniqueness and monotony of generated
id's) to create a document and then update the row with the name of the
document:

    row = AssemblyResult(doc, ...)
    number = row.id
    new_name = construct_name(number, ...)
    doc = create_document(new_name, ...)
    row.doc = doc

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

[SQLObject] Table locking with MySQL

[Jason H. <jas...@gm...>]

I am using SQLObject (0.12.4, but could be later) with MySQL 5.1 as
the storage for a CherryPy based web app. I have a table "assembly"
which refers to another table "assembly_results"; the SQLObject class
def is something like:

    class Assembly(SQLObject):
        dbAssemblyResults = MultipleJoin('AssemblyResult',
joinColumn='db_assembly_id')
        ...

    class AssemblyResult(SQLObject):
        dbAssembly = ForeignKey('Assembly')
        ...

Both tables are InnoDB.

To upload new results, I need to generate a filename that includes an
index of the file, eg. the 5th result uploaded against an assembly is
named "05. Some file...".  So I have the following:

    # asmbly is an instance of Assembly
    number = len(asmbly.dbAssemblyResults) + 1
    new_name = construct_name(number, ...)
    doc = create_document(new_name, ...)
    # create_document returns an instance of another SQLObject subclass
    AssemblyResult(doc, ...)

The trouble is that there's a race hazard here — two uploads at almost
the same time will see the same number of uploaded documents and I'll
end up with two file names with the same index.

The simplest way I could think of to make this safe is to lock the
assembly_result table for the duration of these calls (not
unreasonable in my situation), but I can't find support for table
locking in the SQLObject docs. Is it there, or should I use raw SQL
calls? Or is there a better way?

— Jason

Re: [SQLObject] SQLObject 0.15.0b1

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

On Mon, Nov 22, 2010 at 07:33:48PM +0100, Daniel Fetchinson wrote:
> My app works just as before.
> Thank a lot Oleg for all your work!

   Thank you for the report and the nice words!

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

Re: [SQLObject] SQLObject 0.15.0b1

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

>> * Major API change: all signals are sent with the instance (or the class)
>>   as the first parameter. The following signals were changed:
>>   RowCreateSignal, RowCreatedSignal, DeleteColumnSignal.
>>
>> * Major API change: post-processing functions for all signals are called
>>   with the instance as the first parameter. The following signals were
>>   changed: RowUpdatedSignal, RowDestroySignal, RowDestroyedSignal.
>
>    Due to these major API changes there will be a prolonged beta period.

My app works just as before.
Thank a lot Oleg for all your work!

Cheers,
Daniel


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

Re: [SQLObject] SQLObject 0.15.0b1

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

On Mon, Nov 22, 2010 at 07:36:01PM +0300, Oleg Broytman wrote:
> * Major API change: all signals are sent with the instance (or the class)
>   as the first parameter. The following signals were changed:
>   RowCreateSignal, RowCreatedSignal, DeleteColumnSignal.
> 
> * Major API change: post-processing functions for all signals are called
>   with the instance as the first parameter. The following signals were
>   changed: RowUpdatedSignal, RowDestroySignal, RowDestroyedSignal.

   Due to these major API changes there will be a prolonged beta period.

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

[SQLObject] SQLObject 0.15.0b1

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

Hello!

I'm pleased to announce version 0.15.0b1, the first beta of the upcoming
release of branch 0.15 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.15.0b1dev-r4283

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


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

* Major API change: all signals are sent with the instance (or the class)
  as the first parameter. The following signals were changed:
  RowCreateSignal, RowCreatedSignal, DeleteColumnSignal.

* Major API change: post-processing functions for all signals are called
  with the instance as the first parameter. The following signals were
  changed: RowUpdatedSignal, RowDestroySignal, RowDestroyedSignal.

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

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

Re: [SQLObject] select distinct value from xyz where condition

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

On Tue, Nov 09, 2010 at 07:40:46PM +0000, AlexB wrote:
> Oleg,
> 
> Thank you for the example and the thorough explanation - it worked first time,
> and I learned some more ! 

   You are welcome!

> I'll add the info below to the stackoverflow question as well, citing your name.

   Thank you!

> Regards, Alex.

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

Re: [SQLObject] select distinct value from xyz where condition

[AlexB <as...@te...>]

Oleg,

Thank you for the example and the thorough explanation - it worked first time,
and I learned some more ! 

I'll add the info below to the stackoverflow question as well, citing your name.

Regards, Alex.

Re: [SQLObject] select distinct value from xyz where condition

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

On Mon, Nov 08, 2010 at 09:53:26PM +0000, AlexB wrote:
> I have a specific SQL query that I need:
> 
> select distinct author from blogtable where keyword = "dust";

   One cannot select a column using the high-level SQLObject API, one can
only select all columns at once (*), and it's almost meaningless to query

select distinct *

   SQLBuilder is the mid-level API. To use SQLBuilder first construct the
query:

from sqlobject.sqlbuider import Select

query = Select([BlogTable.q.author], where=BlogTable.q.keyword=='dust', distinct=True)

   and then convert the object to SQL query string and execute the string
using the low-level API:

rows = connection.queryAll(connection.sqlrepr(query))

   The result is a list of rows, every row is a tuple of length 1 (the
author):

for row in rows:
   author = row[0]
   print author

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

[SQLObject] select distinct value from xyz where condition

[AlexB <as...@te...>]

Hello there,

I've asked a question in stackoverflow about the following issue:

http://stackoverflow.com/questions/4120165/how-to-translate-this-to-sqlobject-select-distinct-columnname-where/

So far not many results, I'm hoping to get more info here. I'll update the
stackoverflow quesiton in that case.

In short, a recap from the above page:
"""
I have a specific SQL query that I need:

select distinct author from blogtable where keyword = "dust";

Multiple authors can post about multiple keywords.

The query works on the MySQL database if I use the raw sql query. But I can't
seem to understand what I must do to get this correctly working in SQLObject.

I see heaps of references to sqlbuilder, but the manual page on that is not very
extensive. The examples provided in the google groups also talk as if SQLbuilder
is the answer, but again, no specific example (for my problem) that I can
understand.

Could someone well versed in SQLObject explain to me how I implement the above
SQL in SQLObject ? If not possible, can I pass the raw sql in any way via
SQLObject to the underlying db ?
"""

I've been in and out of this group the last few weeks reading and searching.
I've found several references to possible solutions to this using SQLBuilder,
including a few commands, but I just can't seem to *understand* what is meant by
those commands, nor what exactly sqlbuilder is and how to use it. It's becoming
very frustrating...

IS there a way to do this ? If so, how does SQLBuilder work ? An example would
be really nice and much appreciated !

Regards, Alex

Re: [SQLObject] Managing hierarchical data

[Lutz S. <l.s...@4c...>]

On Thu, 28 Oct 2010 01:09:59 +0000 (UTC)
Mark <mar...@ya...> wrote:

> Is there a recommend way to deal with hierarchical data with SQLObject?
> I think I'm going to simply keep track of my categories and their 
> hierarchy outside of SQLObject classes and then simply have all of my 
> objects contain a category id so I can list them under the proper 
> category. 
> 
> Reference:
> http://dev.mysql.com/tech-resources/articles/hierarchical-data.html

Some nice concepts not only for non SQL DBs:
http://www.mongodb.org/display/DOCS/Trees+in+MongoDB


regards
lutz

Re: [SQLObject] Managing hierarchical data

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

On Thu, Oct 28, 2010 at 08:16:33PM +0000, Mark wrote:
> I can easily set up the 
> tree in my python code and pickle it.

   My not so humble opinion on that is - don't do that. Use portable tools
(portable between languages, I mean in this case). SQL is quite a portable
tool; if your project eventually grows up to include a number of developers
they would want to use different languages for different tasks, for
example, Java to create reports and PHP for quick-and-dirty backoffice; in
this case having a well thought out SQL schema is a big advantage.

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

Re: [SQLObject] Managing hierarchical data

[Mark <mar...@ya...>]

Oleg Broytman <phd <at> phd.pp.ru> writes:

> 
> On Thu, Oct 28, 2010 at 01:09:59AM +0000, Mark wrote:
> > Is there a recommend way to deal with hierarchical data with SQLObject?
> > I think I'm going to simply keep track of my categories and their 
> > hierarchy outside of SQLObject classes and then simply have all of my 
> > objects contain a category id so I can list them under the proper 
> > category. 
> > 
> > Reference:
> > http://dev.mysql.com/tech-resources/articles/hierarchical-data.html
> 
>    See also http://onlamp.com/pub/a/onlamp/2004/08/05/hierarchical_sql.html
> 
> Oleg.

Thanks for the link, it is less taxing on my brain.  I really don't want to put 
this into SQL and figure out the SQLObject handling when I can easily set up the 
tree in my python code and pickle it. But as I'm new to moving my app 
functionality onto the web I worry about how big the tree ends up getting, 
formatting, backup/recovery etc.. 

Re: [SQLObject] Managing hierarchical data

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

On Thu, Oct 28, 2010 at 01:09:59AM +0000, Mark wrote:
> Is there a recommend way to deal with hierarchical data with SQLObject?
> I think I'm going to simply keep track of my categories and their 
> hierarchy outside of SQLObject classes and then simply have all of my 
> objects contain a category id so I can list them under the proper 
> category. 
> 
> Reference:
> http://dev.mysql.com/tech-resources/articles/hierarchical-data.html

   See also http://onlamp.com/pub/a/onlamp/2004/08/05/hierarchical_sql.html

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

[SQLObject] ¡Luis Cota te ha dejado un mensaje en Badoo!

[Badoo <no...@ba...>]

¡Tienes un nuevo mensaje en Badoo!

Luis Cota te dejó un mensaje.
Haz click en este enlace para verlo:
http://us1.badoo.com/lcota/in/hA8J2k7HQhA/?lang_id=7

Más gente que también te está esperando:
Wilber (New York, Estados Unidos)
Sharlotte (New York, Estados Unidos)
Paco (New York, Estados Unidos)

http://us1.badoo.com/lcota/in/hA8J2k7HQhA/?lang_id=7

Si al hacer click sobre el enlace, no funciona, copia y pega la dirección en tu barra del navegador.

Este email es parte del procedimiento para que leas los mensajes de Luis Cota. Si has recibido este email por equivocación, por favor, ignóralo. Tras un corto periodo de tiempo el mensaje sera eliminado del sistema.

¡Diviértete!
El Equipo de Badoo


Has recibido este email porque un usuario de Badoo te ha dejado un mensaje en Badoo. Este mensaje es automático. Las respuestas a este mensaje no estan controladas y no serán contestadas. Si no quieres recibir más mensajes de Badoo, háznoslo saber:
http://us1.badoo.com/impersonation.phtml?lang_id=7&mail_code=63&email=sqlobject-discuss%40lists.sourceforge.net&secret=&invite_id=435256&user_id=1093354112

[SQLObject] Managing hierarchical data

[Mark <mar...@ya...>]

Is there a recommend way to deal with hierarchical data with SQLObject?
I think I'm going to simply keep track of my categories and their 
hierarchy outside of SQLObject classes and then simply have all of my 
objects contain a category id so I can list them under the proper 
category. 

Reference:
http://dev.mysql.com/tech-resources/articles/hierarchical-data.html

Mark

Re: [SQLObject] Auto reconnect with postgres

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

On Wed, Oct 20, 2010 at 10:47:41AM +0200, Gert Burger wrote:
> SQLObject doesn't seem to reconnect to a postgres DB when its
> connection(s) are lost. Is SO capable of reconnecting?
> 
> I saw a few post related to SO and Mysql but nothing related to PG.
> 
> A grep of the source also shows that only mysqlconnection.py has
> reconnect logic in it.

   MySQL can automagically reconnect by calling connection.ping(True) -
after that if client library notes a connection is lost it tries to
reconnect. Users must understand though that automatic reconnect has its
set of problems; see
http://dev.mysql.com/doc/refman/5.0/en/auto-reconnect.html for details.

   PostgreSQL's client library doesn't do a reconnect exactly to avoid
these problems. On the other hand having timed out connections in
SQLObject's pool is a problem, I understand. There have to be a way to
remove them from the pool to force SQLObject to open new connections.

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

[SQLObject] Auto reconnect with postgres

[Gert B. <ger...@gm...>]

Hi

SQLObject doesn't seem to reconnect to a postgres DB when its
connection(s) are lost. Is SO capable of reconnecting?

I saw a few post related to SO and Mysql but nothing related to PG.

A grep of the source also shows that only mysqlconnection.py has
reconnect logic in it.

-- 
Regards
Gert Burger

[SQLObject] SQLObject 0.14.1

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

Hello!

I'm pleased to announce version 0.14.1, a minor bugfix release of branch
0.14 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/0.14.1

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


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

News since 0.14.0
-----------------

* A bug was fixed in a subtle case when a per-instance connection is not
  passed to validators.

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

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

[SQLObject] SQLObject 0.13.1

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

Hello!

I'm pleased to announce version 0.13.1, a minor bugfix release of branch
0.13 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/0.13.1

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


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

News since 0.13.0
-----------------

* A bug was fixed in a subtle case when a per-instance connection is not
  passed to validators.

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

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

Re: [SQLObject] q-magic + multiple connections

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

On Thu, Oct 14, 2010 at 02:04:39AM -0700, Octav Chipara wrote:
> I applied the patch to my sqlobject version and now it passes the test
> program I sent earlier. Thank you for your help.

   Thank you for the report!

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

Re: [SQLObject] q-magic + multiple connections

[Octav C. <och...@gm...>]

Hi Oleg,

I applied the patch to my sqlobject version and now it passes the test
program I sent earlier. Thank you for your help.

-- Octav

On Thu, Oct 14, 2010 at 1:56 AM, Oleg Broytman <ph...@ph...> wrote:

> On Thu, Oct 14, 2010 at 01:47:05AM -0700, Octav Chipara wrote:
> > Unfortunately, I could not locate the patch file. Could you please send
> it
> > to me and I will apply it and test it?
>
>    Sent by private email.
>
> > Are the changes already in svn?
>
>    Not yet. I was going to test it thoroughly today but now I will wait
> until your report.
>
> Oleg.
> --
>     Oleg Broytman            http://phd.pp.ru/            ph...@ph...
>           Programmers don't die, they just GOSUB without RETURN.
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>

Re: [SQLObject] q-magic + multiple connections

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

On Thu, Oct 14, 2010 at 01:47:05AM -0700, Octav Chipara wrote:
> Unfortunately, I could not locate the patch file. Could you please send it
> to me and I will apply it and test it?

   Sent by private email.

> Are the changes already in svn?

   Not yet. I was going to test it thoroughly today but now I will wait
until your report.

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

Re: [SQLObject] q-magic + multiple connections

[Octav C. <och...@gm...>]

Oleg,

Unfortunately, I could not locate the patch file. Could you please send it
to me and I will apply it and test it? Are the changes already in svn?

Thanks,
-- Octav

On Thu, Oct 14, 2010 at 1:27 AM, Oleg Broytman <ph...@ph...> wrote:

> Hello!
>
> On Wed, Oct 13, 2010 at 04:48:44PM -0700, Octav Chipara wrote:
> > This also fails to work with selectby as shown in the example below. It
> > looks like IntCols can be handled correctly but StringCol cannot.
> >
> > >   File
> > >
> "/Library/Python/2.6/site-packages/SQLObject-0.13.0-py2.6.egg/sqlobject/sqlbuilder.py",
> > > line 341, in _from_python
> > >     value = column.from_python(value, SQLObjectState(self.soClass))
> > >   File
> > >
> "/Library/Python/2.6/site-packages/SQLObject-0.13.0-py2.6.egg/sqlobject/col.py",
> > > line 501, in to_python
> > >     connection = state.soObject._connection
> > >   File
> > >
> "/Library/Python/2.6/site-packages/SQLObject-0.13.0-py2.6.egg/sqlobject/dbconnection.py",
> > > line 837, in __get__
> > >     return self.getConnection()
> > >   File
> > >
> "/Library/Python/2.6/site-packages/SQLObject-0.13.0-py2.6.egg/sqlobject/dbconnection.py",
> > > line 850, in getConnection
> > >     "No connection has been defined for this thread "
> > > AttributeError: No connection has been defined for this thread or
> process
> > > Exception AttributeError: "'NoneType' object has no attribute
> 'print_exc'"
> > > in <function _removeReceiver at 0x1004e3398> ignored
>
>    You stumbled over exactly the same problem that was discussed a day or
> two ago - sometimes validators (especially validators for StringCol) need
> to know the current connection (StringCol's validator needs to know
> charset/encoding). Please test the patch that I sent and report back if it
> helps.
>
> Oleg.
> --
>     Oleg Broytman            http://phd.pp.ru/            ph...@ph...
>           Programmers don't die, they just GOSUB without RETURN.
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>