sqlobject-discuss — All things SQLObject-related

Re: [SQLObject] Vacation

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

> Hi, all! I am on vacation till 11 of April.

Have fun! We promise we will be nice to each other :)

Cheers,
Daniel


> Oleg.
> --
>      Oleg Broytman            http://phdru.name/            ph...@ph...
>            Programmers don't die, they just GOSUB without RETURN.
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>


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

[SQLObject] Vacation

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

Hi, all! I am on vacation till 11 of April.

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

Re: [SQLObject] Newbie question on Many-to-Many intermediate tables (example?)

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

On Mon, Mar 28, 2011 at 01:49:17PM -0600, Pгoм???тн?????s 0x01 wrote:
> Hi all,
> 
> First, I would like to say that I think SQLObject is one of the better ORM
> wrappers I have looked at, and I really like how you all have made it feel
> really natural within Python.

   Welcome!

> I've been reading through the documentation and I was wondering if there was
> any examples of how one could do a many-to-many relationship such that the
> intermediate table had additional attributes? I saw this hinted at in the
> documentation, but I guess I missed a relevant example.

http://sqlobject.org/FAQ.html#how-can-i-define-my-own-intermediate-table-in-my-many-to-many-relationship

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

[SQLObject] Newbie question on Many-to-Many intermediate tables (example?)

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

Hi all,

First, I would like to say that I think SQLObject is one of the better ORM
wrappers I have looked at, and I really like how you all have made it feel
really natural within Python.

I've been reading through the documentation and I was wondering if there was
any examples of how one could do a many-to-many relationship such that the
intermediate table had additional attributes? I saw this hinted at in the
documentation, but I guess I missed a relevant example.

For instance, going back to to the example in the documentation (see:
http://sqlobject.org/SQLObject.html#many-to-many-relationships ) -- how
would the DateTime column be added to the intermediate table? Or even a
'comment' StringCol? (So that the date of role-adding could be put in, as
well as a "reason")

Thanks in advance!

Re: [SQLObject] SQLObject 1.0.0

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

On Mon, Mar 28, 2011 at 07:55:49PM +0200, Daniel Fetchinson wrote:
> > Congratulations!
> >
> > I'd like to thank you Oleg for working on this project and giving it your
> > time. It does not go unappreciated :)
> >
> > Cheers,
> > Imri
> 
> I'd like to second that!
> Thanks a million, Oleg!
> I use sqlobject a lot and without all your work my projects would not
> be possible.
> 
> Cheers,
> Daniel

   Thank you very much!

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

Re: [SQLObject] SQLObject 1.0.0

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

> Congratulations!
>
> I'd like to thank you Oleg for working on this project and giving it your
> time. It does not go unappreciated :)
>
> Cheers,
> Imri

I'd like to second that!
Thanks a million, Oleg!
I use sqlobject a lot and without all your work my projects would not
be possible.

Cheers,
Daniel


>> Hello!
>>
>> I'm really happy to announce SQLObject version 1.0.0!
>>
>>
>> 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/1.0.0
>>
>> News and changes:
>> http://sqlobject.org/News.html
>>
>>
>> What's New
>> ==========
>>
>> Features & Interface
>> --------------------
>>
>> * Major API change: DB URI parser was changed to use urllib.split*() and
>>  unquote(). This means any username/password/path are allowed in DB
>>  URIs if they are properly %-encoded, and DB URIs are automatically
>>  unquoted.
>>
>> * A new module ``__version__.py`` was added. New variables ``version``
>>  (string) and ``version_info`` (5-tuple: major, minor, micro, release
>>  level, serial) are imported into ``sqlobject`` namespace.
>>
>> * In SQLite, id columns are made AUTOINCREMENT.
>>
>> * Parameter ``backend`` in DB URI is no longer supported, use parameter
>>  ``driver``.
>>
>> 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.
>>
>>
>> ------------------------------------------------------------------------------
>> Enable your software for Intel(R) Active Management Technology to meet the
>> growing manageability and security demands of your customers. Businesses
>> are taking advantage of Intel(R) vPro (TM) technology - will your software
>> be a part of the solution? Download the Intel(R) Manageability Checker
>> today! http://p.sf.net/sfu/intel-dev2devmar
>> _______________________________________________
>> sqlobject-discuss mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>>
>


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

Re: [SQLObject] SQLObject 1.0.0

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

On Mon, Mar 28, 2011 at 04:11:02PM +0200, Imri Goldberg wrote:
> Congratulations!
> 
> I'd like to thank you Oleg for working on this project and giving it your
> time. It does not go unappreciated :)
> 
> Cheers,
> Imri

   Thank you very much!

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

Re: [SQLObject] SQLObject 1.0.0

[Imri G. <lor...@gm...>]

Congratulations!

I'd like to thank you Oleg for working on this project and giving it your
time. It does not go unappreciated :)

Cheers,
Imri


-- 
Imri Goldberg
--------------------------------------
http://plnnr.com/ - automatic trip planning
http://www.algorithm.co.il/blogs/
--------------------------------------
-- insert signature here ----

On Mon, Mar 28, 2011 at 3:26 PM, Oleg Broytman <ph...@ph...> wrote:

> Hello!
>
> I'm really happy to announce SQLObject version 1.0.0!
>
>
> 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/1.0.0
>
> News and changes:
> http://sqlobject.org/News.html
>
>
> What's New
> ==========
>
> Features & Interface
> --------------------
>
> * Major API change: DB URI parser was changed to use urllib.split*() and
>  unquote(). This means any username/password/path are allowed in DB
>  URIs if they are properly %-encoded, and DB URIs are automatically
>  unquoted.
>
> * A new module ``__version__.py`` was added. New variables ``version``
>  (string) and ``version_info`` (5-tuple: major, minor, micro, release
>  level, serial) are imported into ``sqlobject`` namespace.
>
> * In SQLite, id columns are made AUTOINCREMENT.
>
> * Parameter ``backend`` in DB URI is no longer supported, use parameter
>  ``driver``.
>
> 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.
>
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>

[SQLObject] SQLObject 1.0.0

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

Hello!

I'm really happy to announce SQLObject version 1.0.0!


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/1.0.0

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


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

Features & Interface
--------------------

* Major API change: DB URI parser was changed to use urllib.split*() and
  unquote(). This means any username/password/path are allowed in DB
  URIs if they are properly %-encoded, and DB URIs are automatically
  unquoted.

* A new module ``__version__.py`` was added. New variables ``version``
  (string) and ``version_info`` (5-tuple: major, minor, micro, release
  level, serial) are imported into ``sqlobject`` namespace.

* In SQLite, id columns are made AUTOINCREMENT.

* Parameter ``backend`` in DB URI is no longer supported, use parameter
  ``driver``.

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] Enhanced IN Operator, interest in patch?

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

On Tue, Mar 22, 2011 at 12:01:54PM +0300, Oleg Broytman wrote:
> query = list_.queryForSelect()
> query.ops['items'] = [list_.sourceClass.q.id]

   I added a test and committed in the revsion 4371:
http://sourceforge.net/mailarchive/forum.php?thread_name=E1Q2l8p-0002iI-Nr%40webwareforpython.org&forum_name=sqlobject-cvs
   Thank you!

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

[SQLObject] SQLObject 1.0.0b2

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

Hello!

I'm pleased to announce version 1.0.0b2, the second beta of the upcoming
release of branch 1.0 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/1.0.0b2dev-r4370

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


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

Features & Interface
--------------------

* A new module ``__version__.py`` was added. New variables ``version``
  (string) and ``version_info`` (5-tuple: major, minor, micro, release
  level, serial) are imported into ``sqlobject`` namespace.

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 0.15.1

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

Hello!

I'm pleased to announce version 0.15.1, a bugfix 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.1

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


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

* A bug was fixed in MSSQLConnection.

* A minor bug was fixed in sqlbuilder.Union.

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] Enhanced IN Operator, interest in patch?

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

On Tue, Mar 22, 2011 at 10:26:22AM +0100, Gregor Horvath wrote:
> But I would prefer to make an optional argument 'columns' to
> queryForSelect, because it is not obvious that the columns / items can
> be changed after initialisation.
> 
> so it would be 
> 
> list_ = list_.queryForSelect(columns=[list_.sourceClass.q.id])

   Hmm... I don't like this approach, at least at the first glance. I
have to think about it, but now I'd rather split queryForSelect into two
functions. Something like this:

    def queryForSelect(self):
        columns = [self.sourceClass.q.id] + [getattr(self.sourceClass.q, x.name) for x in self.sourceClass.sqlmeta.columnList]
        return self.makeQuery(columns)

    def makeQuery(self, columns):
        query = sqlbuilder.Select(columns,
            ...

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

Re: [SQLObject] Enhanced IN Operator, interest in patch?

[Gregor H. <gh...@gr...>]

Hi,

On Tue, 22 Mar 2011 12:01:54 +0300
Oleg Broytman <ph...@ph...> wrote:

> Hi!
> 
> On Tue, Mar 22, 2011 at 09:27:04AM +0100, Gregor Horvath wrote:
> > def IN_(item, list_):
> >     if isinstance(list_, SelectResults):
> >         list_ = Select([list_.sourceClass.q.id],
> >                        where=list_.clause,
> >                        join=list_.ops.get('join', NoDefault),
> >                        distinct=list_.ops.get('distinct',False),
> >                        lazyColumns=list_.ops.get('lazyColumns',
> > False), start=list_.ops.get('start', 0),
> >                        end=list_.ops.get('end', None),
> >                        orderBy=list_.ops.get('dbOrderBy',
> > NoDefault), reversed=list_.ops.get('reversed', False),
> >                        staticTables=list_.tables,
> >                        forUpdate=list_.ops.get('forUpdate', False))
> 
>    Isn't this just
> 
> query = list_.queryForSelect()
> query.ops['items'] = [list_.sourceClass.q.id]
> 
>

Thank You. Yes this is equivalent and more compact.
But I would prefer to make an optional argument 'columns' to
queryForSelect, because it is not obvious that the columns / items can
be changed after initialisation.

so it would be 

list_ = list_.queryForSelect(columns=[list_.sourceClass.q.id])

--
Gregor

Re: [SQLObject] Enhanced IN Operator, interest in patch?

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

Hi!

On Tue, Mar 22, 2011 at 09:27:04AM +0100, Gregor Horvath wrote:
> def IN_(item, list_):
>     if isinstance(list_, SelectResults):
>         list_ = Select([list_.sourceClass.q.id],
>                        where=list_.clause,
>                        join=list_.ops.get('join', NoDefault),
>                        distinct=list_.ops.get('distinct',False),
>                        lazyColumns=list_.ops.get('lazyColumns', False),
>                        start=list_.ops.get('start', 0),
>                        end=list_.ops.get('end', None),
>                        orderBy=list_.ops.get('dbOrderBy', NoDefault),
>                        reversed=list_.ops.get('reversed', False),
>                        staticTables=list_.tables,
>                        forUpdate=list_.ops.get('forUpdate', False))

   Isn't this just

query = list_.queryForSelect()
query.ops['items'] = [list_.sourceClass.q.id]

   ?

>     return IN(item, query)

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

[SQLObject] Enhanced IN Operator, interest in patch?

[Gregor H. <gh...@gr...>]

Hi,

I've made an enhanced sqlbuilder IN Operator for my own purpose and
would like to ask if there is any interest in a patch for the
sqlbuilder IN operator.

It's enhancement is the ability to deal with SelectResults in addition
to the standard sqlbuilder.Select. The motivation is the need to
create subqueries using previously acquired SelectResults.

def IN_(item, list_):
    if isinstance(list_, SelectResults):
        list_ = Select([list_.sourceClass.q.id],
                       where=list_.clause,
                       join=list_.ops.get('join', NoDefault),
                       distinct=list_.ops.get('distinct',False),
                       lazyColumns=list_.ops.get('lazyColumns', False),
                       start=list_.ops.get('start', 0),
                       end=list_.ops.get('end', None),
                       orderBy=list_.ops.get('dbOrderBy', NoDefault),
                       reversed=list_.ops.get('reversed', False),
                       staticTables=list_.tables,
                       forUpdate=list_.ops.get('forUpdate', False))
    return IN(item, list_)

--
Greg

Re: [SQLObject] bug report: limit(num) method for Firebird

[Joe L. <joe...@gm...>]

Great!  Thank you.

On Thu, Mar 17, 2011 at 12:20 PM, Oleg Broytman <ph...@ph...> wrote:

> On Wed, Mar 16, 2011 at 11:08:52PM +0300, Oleg Broytman wrote:
> > On Wed, Mar 16, 2011 at 02:33:48PM -0400, Joe Lanese wrote:
> > > I just came across the exact same problem using the mssql connection
> > > (mssqlconnection.py).  More specifically the problem occured when I
> tried to
> > > access the first returned row of a selectResults (ie. selResults[0]).
>  I
> > > tried the same solution below in the mssqlconnection.py file, and it
> solved
> > > the problem.
> > >
> > > Can this fix also be applied to the official mssql support?
> > >
> > > > On Fri, Dec 18, 2009 at 01:19:25AM +0100, Petr Jake?? wrote:
> > > > Index: firebirdconnection.py
> > > > ===================================================================
> > > > --- firebirdconnection.py       (revision 4047)
> > > > +++ firebirdconnection.py       (working copy)
> > > > @@ -10,6 +10,8 @@
> > > >     dbName = 'firebird'
> > > >     schemes = [dbName]
> > > >
> > > > +    limit_re = re.compile('^\s*(select )(.*)', re.IGNORECASE)
> >
> >    Thank you, I'll apply the patch tomorrow. New releases will be
> > released in a few days.
>
>   Applied and committed in the revisions 4358-4360 (branches 0.15, 1.0
> and the trunk; I've stopped maintaining branch 0.14 as I am releasing
> version 1.0 RSN.)
>
> Oleg.
> --
>     Oleg Broytman            http://phdru.name/            ph...@ph...
>           Programmers don't die, they just GOSUB without RETURN.
>
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>

Re: [SQLObject] bug report: limit(num) method for Firebird

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

On Wed, Mar 16, 2011 at 11:08:52PM +0300, Oleg Broytman wrote:
> On Wed, Mar 16, 2011 at 02:33:48PM -0400, Joe Lanese wrote:
> > I just came across the exact same problem using the mssql connection
> > (mssqlconnection.py).  More specifically the problem occured when I tried to
> > access the first returned row of a selectResults (ie. selResults[0]).  I
> > tried the same solution below in the mssqlconnection.py file, and it solved
> > the problem.
> > 
> > Can this fix also be applied to the official mssql support?
> > 
> > > On Fri, Dec 18, 2009 at 01:19:25AM +0100, Petr Jake?? wrote:
> > > Index: firebirdconnection.py
> > > ===================================================================
> > > --- firebirdconnection.py       (revision 4047)
> > > +++ firebirdconnection.py       (working copy)
> > > @@ -10,6 +10,8 @@
> > >     dbName = 'firebird'
> > >     schemes = [dbName]
> > >
> > > +    limit_re = re.compile('^\s*(select )(.*)', re.IGNORECASE)
> 
>    Thank you, I'll apply the patch tomorrow. New releases will be
> released in a few days.

   Applied and committed in the revisions 4358-4360 (branches 0.15, 1.0
and the trunk; I've stopped maintaining branch 0.14 as I am releasing
version 1.0 RSN.)

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

Re: [SQLObject] bug report: limit(num) method for Firebird

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

On Wed, Mar 16, 2011 at 02:33:48PM -0400, Joe Lanese wrote:
> I just came across the exact same problem using the mssql connection
> (mssqlconnection.py).  More specifically the problem occured when I tried to
> access the first returned row of a selectResults (ie. selResults[0]).  I
> tried the same solution below in the mssqlconnection.py file, and it solved
> the problem.
> 
> Can this fix also be applied to the official mssql support?
> 
> > On Fri, Dec 18, 2009 at 01:19:25AM +0100, Petr Jake?? wrote:
> > Index: firebirdconnection.py
> > ===================================================================
> > --- firebirdconnection.py       (revision 4047)
> > +++ firebirdconnection.py       (working copy)
> > @@ -10,6 +10,8 @@
> >     dbName = 'firebird'
> >     schemes = [dbName]
> >
> > +    limit_re = re.compile('^\s*(select )(.*)', re.IGNORECASE)

   Thank you, I'll apply the patch tomorrow. New releases will be
released in a few days.

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

Re: [SQLObject] bug report: limit(num) method for Firebird

[Joe L. <joe...@gm...>]

Hi,
I just came across the exact same problem using the mssql connection
(mssqlconnection.py).  More specifically the problem occured when I tried to
access the first returned row of a selectResults (ie. selResults[0]).  I
tried the same solution below in the mssqlconnection.py file, and it solved
the problem.

Can this fix also be applied to the official mssql support?

Thanks,
Joe

On Sun, Dec 20, 2009 at 10:41 AM, Oleg Broytman <ph...@ph...> wrote:

> Hi!
>
> On Fri, Dec 18, 2009 at 01:19:25AM +0100, Petr Jake?? wrote:
> >   File
> >
> "/usr/lib/python2.5/site-packages/SQLObject-0.10.1-py2.5.egg/sqlobject/firebird/firebirdconnection.py",
> > line 120, in _queryAddLimitOffset
> >     match = cls.limit_re.match(query)
> > AttributeError: class FirebirdConnection has no attribute 'limit_re'
>
>   This is the patch that I think fixes the problem:
>
> Index: firebirdconnection.py
> ===================================================================
> --- firebirdconnection.py       (revision 4047)
> +++ firebirdconnection.py       (working copy)
> @@ -10,6 +10,8 @@
>     dbName = 'firebird'
>     schemes = [dbName]
>
> +    limit_re = re.compile('^\s*(select )(.*)', re.IGNORECASE)
> +
>     def __init__(self, host, db, user='sysdba',
>                  password='masterkey', autoCommit=1,
>                  dialect=None, role=None, charset=None, **kw):
> @@ -18,8 +20,6 @@
>             import kinterbasdb
>         self.module = kinterbasdb
>
> -        self.limit_re = re.compile('^\s*(select )(.*)', re.IGNORECASE)
> -
>         self.host = host
>         self.db = db
>         self.user = user
>
> Oleg.
> --
>     Oleg Broytman            http://phd.pp.ru/            ph...@ph...
>           Programmers don't die, they just GOSUB without RETURN.
>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>

Re: [SQLObject] deleting an intermediate table

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

On Mon, Mar 14, 2011 at 11:40:24AM +0000, Timothy W. Grove wrote:
> If I have an old database which contains an intermediate table generated 
> by code such as 'videos = RelatedJoin("ExplanatoryVideos")' , and the 
> class has been changed to no longer require a 'many-to-many' 
> relationship, can this intermediate table be deleted through SQLObject 
> to update the old database?

   Table.dropJoinTables() drops all intermediate tables. If you want to
drop only a specific table, you ought to copy some code from
.dropJoinTables() to find out what table you want to drop - and drop it.

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

[SQLObject] deleting an intermediate table

[Timothy W. G. <tim...@si...>]

If I have an old database which contains an intermediate table generated 
by code such as 'videos = RelatedJoin("ExplanatoryVideos")' , and the 
class has been changed to no longer require a 'many-to-many' 
relationship, can this intermediate table be deleted through SQLObject 
to update the old database?

Tim

Re: [SQLObject] SQLObject 1.0.0b1

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

On Wed, Mar 09, 2011 at 07:40:27PM +0100, Daniel Fetchinson wrote:
> Wooohoooo! Version 1.0 beta! :)
> 
> My app works perfectly with the new version!

   Thank you for the report!

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

Re: [SQLObject] SQLObject 1.0.0b1

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

>> * Major API change: DB URI parser was changed to use urllib.split*() and
>>   unquote(). This means any username/password/path are allowed in DB
>>   URIs if they are properly %-encoded, and DB URIs are automatically
>>   unquoted.
>
>    I have been trying to preserve backward compatibility as much as
> possible. Most URIs are not affected at all. Dirty trick with w32 paths
> (C|/path instead of C:/path) is still supported, though C:/path is now
> the recommended syntax. Old API is preserved:
> connectionForURI(uri, oldUri=True), DBConnection.connectionFromOldURI(),
> DBConnection.oldURI(). There is a script sqlobject-convertOldURI that
> accepts old-style URI at the command line and prints to stdout the URI
> in the new format.
>    Anyway - a prolonged beta period.

Wooohoooo! Version 1.0 beta! :)

My app works perfectly with the new version!

Thanks a million,
Daniel

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

Re: [SQLObject] Another newbie question: copying objects?

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

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

On Wed, Mar 09, 2011 at 09:34:21AM -0800, Mark McWiggins wrote:
> What about the connection argument? Do I have to just add that to the dict?

   You can, it's just a normal dictionary. Or you can pass it to the
call:

> On Mar 9, 2011, at 2:43 AM, Oleg Broytman wrote:
> >   You can convert a row to a dict: z.sqlmeta.asDict() - and pass the
> > dict back: newz = zipcode(**z.sqlmeta.asDict())

    newz = zipcode(connection=myconnection, **z.sqlmeta.asDict())

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