sqlobject-discuss — All things SQLObject-related

[SQLObject] SQLObject 1.3.0

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

Hello!

I'm pleased to announce version 1.3.0, the first stable release of branch
1.3 of SQLObject.


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

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

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


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

Site:
http://sqlobject.org

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

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

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

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

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


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

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

* PostgresConnection performs translation of exceptions to standard
  SQLObject's hierarchy of exceptions.

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

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] SqlObject Sqlmeta fromDatabase problem

[Jeremy H. <jer...@gm...>]

Ok.. thank you. I was under the impression that this function will add an
column automatically to my database after I included it in my class. I
might code this functionality into sqlmeta. I would find this to be very
useful for future changes.

Jeremy

On Tue, Mar 27, 2012 at 5:32 AM, Oleg Broytman <ph...@ph...> wrote:

> On Tue, Mar 27, 2012 at 05:27:45AM -0500, Jeremy Hoyle wrote:
> > I added a stringcol to the class Company(SQLObject) table but it did not
> > auto update my database with the column.
>
>    You've got it in the reverse direction. fromDatase gets the list of
> columns *from* database. If you want to add a column from python to
> database you ought to use sqlmeta.addColumn() with changeSchema set to
> True.
>
> Oleg.
> --
>     Oleg Broytman            http://phdru.name/            ph...@ph...
>           Programmers don't die, they just GOSUB without RETURN.
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>

Re: [SQLObject] SqlObject Sqlmeta fromDatabase problem

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

On Tue, Mar 27, 2012 at 05:27:45AM -0500, Jeremy Hoyle wrote:
> I added a stringcol to the class Company(SQLObject) table but it did not
> auto update my database with the column.

   You've got it in the reverse direction. fromDatase gets the list of
columns *from* database. If you want to add a column from python to
database you ought to use sqlmeta.addColumn() with changeSchema set to
True.

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

Re: [SQLObject] SqlObject Sqlmeta fromDatabase problem

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

On Mon, Mar 26, 2012 at 08:02:22PM -0500, Jeremy Hoyle wrote:
>  fromDatabase boolean doesn't seem to be performing its stated function.It
> does not update the database when i enter a new column in the database.

   I have problems understanding the sentence. Did you add a column to
your database and then restarted the program? The program didn't
discover the new column? You can test the list of columns by printing
Company.sqlmeta.columnList and Company.sqlmeta.columns.

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

Re: [SQLObject] SqlObject Sqlmeta fromDatabase problem

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

> fromDatabase: A boolean (default false). If true, then on class creation
> the database will be queried for the table's columns, and any missing
> columns (possible all columns) will be added automatically.
> I started with these
> class Company(SQLObject):
> class sqlmeta:
>         fromDatabase = True
>         lazyUpdate = False
>         cacheValues = True
>     Company_Name = StringCol(length = 256, default = None)
>     Company_Address = StringCol(length = 256, default = None)
>     Company_Phone = StringCol(length = 256, default = None)
>
> Added
> class Company(SQLObject):
> class sqlmeta:
>         fromDatabase = True
>         lazyUpdate = False
>         cacheValues = True
>     Company_Name = StringCol(length = 256, default = None)
>     Company_Address = StringCol(length = 256, default = None)
>     Company_Phone = StringCol(length = 256, default = None)
>     *Company_Number = StringCol(length = 256, default = None)*
>
> class Companys():
>     def __init__(self):
>          Company.createTable(ifNotExists = True, connection=conn)
>
>
>
Hi Jeremy,
what about the Naming Style?
see: Changing the Naming Style <http://sqlobject.org/SQLObject.html#id56>
.... By default names in SQLObject are expected to be mixed case in Python
(like mixedCase), and underscore-separated in SQL (like mixed_case). This
applies to table and column names.

Regards

Petr

Re: [SQLObject] SqlObject Sqlmeta fromDatabase problem

[Jeremy H. <jer...@gm...>]

Sorry.. the previous post was in error.
Thank you for your help but although I am not receiving any errors. The
 fromDatabase boolean doesn't seem to be performing its stated function.It
does not update the database when i enter a new column in the database.

fromDatabase:A boolean (default false). If true, then on class creation the
database will be queried for the table's columns, and any missing columns
(possible all columns) will be added automatically.
I started with these
class Company(SQLObject):
class sqlmeta:
        fromDatabase = True
        lazyUpdate = False
        cacheValues = True
    Company_Name = StringCol(length = 256, default = None)
    Company_Address = StringCol(length = 256, default = None)
    Company_Phone = StringCol(length = 256, default = None)

Added
class Company(SQLObject):
class sqlmeta:
        fromDatabase = True
        lazyUpdate = False
        cacheValues = True
    Company_Name = StringCol(length = 256, default = None)
    Company_Address = StringCol(length = 256, default = None)
    Company_Phone = StringCol(length = 256, default = None)
    *Company_Number = StringCol(length = 256, default = None)*

class Companys():
    def __init__(self):
         Company.createTable(ifNotExists = True, connection=conn)

Output:>>
 2/QueryAll:  SHOW COLUMNS FROM store
 2/QueryAll:  SHOW COLUMNS FROM company
 2/Query   :  DESCRIBE company
 2/Query   :  DESCRIBE store

On Mon, Mar 26, 2012 at 7:55 PM, Jeremy Hoyle <jer...@gm...>wrote:

> Thank you for your help but although I am not receiving any errors. The
>  fromDatabase boolean doesn't seem to be performing its stated function.
>
> fromDatabase: A boolean (default false). If true, then on class creation
> the database will be queried for the table's columns, and any missing
> columns (possible all columns) will be added automatically.
> I started with these
> class Company(SQLObject):
> class sqlmeta:
>         fromDatabase = True
>         lazyUpdate = False
>         cacheValues = True
>     Company_Name = StringCol(length = 256, default = None)
>     Company_Address = StringCol(length = 256, default = None)
>     Company_Phone = StringCol(length = 256, default = None)
>
> Added
> class Company(SQLObject):
> class sqlmeta:
>         fromDatabase = True
>         lazyUpdate = False
>         cacheValues = True
>     Company_Name = StringCol(length = 256, default = None)
>     Company_Address = StringCol(length = 256, default = None)
>     Company_Phone = StringCol(length = 256, default = None)
>  Company_Phone = StringCol(length = 256, default = None)
> On Mon, Mar 26, 2012 at 8:16 AM, Jeremy Hoyle <jer...@gm...>wrote:
>
>> Ok. I got it. I just defined the connection above and outside the
>> Companys and Company classes. Thanks for your help.
>>
>> Jeremy
>>
>>
>> On Mon, Mar 26, 2012 at 8:05 AM, Oleg Broytman <ph...@ph...> wrote:
>>
>>> On Mon, Mar 26, 2012 at 07:59:39AM -0500, Jeremy Hoyle wrote:
>>> >   File "C:\Pysoft\Software\SMS Development\tests\test0.py", line 5, in
>>> > <module>
>>> >     from pySMS import Companys
>>> >   File "C:\Pysoft\Software\SMS Development\pySMS\__init__.py", line 1,
>>> in
>>> > <module>
>>> >     from Company import Companys
>>>
>>>    Here is the problem now - Company (and Companys) is imported before
>>> a connection is created. You have to open a connection before the class
>>> Company is created (i.e., before the module is imported).
>>>
>>> Oleg.
>>> --
>>>     Oleg Broytman            http://phdru.name/
>>> ph...@ph...
>>>           Programmers don't die, they just GOSUB without RETURN.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF email is sponsosred by:
>>> Try Windows Azure free for 90 days Click Here
>>> http://p.sf.net/sfu/sfd2d-msazure
>>> _______________________________________________
>>> sqlobject-discuss mailing list
>>> sql...@li...
>>> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>>>
>>
>>
>

Re: [SQLObject] SqlObject Sqlmeta fromDatabase problem

[Jeremy H. <jer...@gm...>]

Thank you for your help but although I am not receiving any errors. The
 fromDatabase boolean doesn't seem to be performing its stated function.

fromDatabase:A boolean (default false). If true, then on class creation the
database will be queried for the table's columns, and any missing columns
(possible all columns) will be added automatically.
I started with these
class Company(SQLObject):
class sqlmeta:
        fromDatabase = True
        lazyUpdate = False
        cacheValues = True
    Company_Name = StringCol(length = 256, default = None)
    Company_Address = StringCol(length = 256, default = None)
    Company_Phone = StringCol(length = 256, default = None)

Added
class Company(SQLObject):
class sqlmeta:
        fromDatabase = True
        lazyUpdate = False
        cacheValues = True
    Company_Name = StringCol(length = 256, default = None)
    Company_Address = StringCol(length = 256, default = None)
    Company_Phone = StringCol(length = 256, default = None)
 Company_Phone = StringCol(length = 256, default = None)
On Mon, Mar 26, 2012 at 8:16 AM, Jeremy Hoyle <jer...@gm...>wrote:

> Ok. I got it. I just defined the connection above and outside the Companys
> and Company classes. Thanks for your help.
>
> Jeremy
>
>
> On Mon, Mar 26, 2012 at 8:05 AM, Oleg Broytman <ph...@ph...> wrote:
>
>> On Mon, Mar 26, 2012 at 07:59:39AM -0500, Jeremy Hoyle wrote:
>> >   File "C:\Pysoft\Software\SMS Development\tests\test0.py", line 5, in
>> > <module>
>> >     from pySMS import Companys
>> >   File "C:\Pysoft\Software\SMS Development\pySMS\__init__.py", line 1,
>> in
>> > <module>
>> >     from Company import Companys
>>
>>    Here is the problem now - Company (and Companys) is imported before
>> a connection is created. You have to open a connection before the class
>> Company is created (i.e., before the module is imported).
>>
>> Oleg.
>> --
>>     Oleg Broytman            http://phdru.name/            ph...@ph...
>>           Programmers don't die, they just GOSUB without RETURN.
>>
>>
>> ------------------------------------------------------------------------------
>> This SF email is sponsosred by:
>> Try Windows Azure free for 90 days Click Here
>> http://p.sf.net/sfu/sfd2d-msazure
>> _______________________________________________
>> sqlobject-discuss mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>>
>
>

Re: [SQLObject] SqlObject Sqlmeta fromDatabase problem

[Jeremy H. <jer...@gm...>]

Ok. I got it. I just defined the connection above and outside the Companys
and Company classes. Thanks for your help.

Jeremy

On Mon, Mar 26, 2012 at 8:05 AM, Oleg Broytman <ph...@ph...> wrote:

> On Mon, Mar 26, 2012 at 07:59:39AM -0500, Jeremy Hoyle wrote:
> >   File "C:\Pysoft\Software\SMS Development\tests\test0.py", line 5, in
> > <module>
> >     from pySMS import Companys
> >   File "C:\Pysoft\Software\SMS Development\pySMS\__init__.py", line 1, in
> > <module>
> >     from Company import Companys
>
>    Here is the problem now - Company (and Companys) is imported before
> a connection is created. You have to open a connection before the class
> Company is created (i.e., before the module is imported).
>
> Oleg.
> --
>     Oleg Broytman            http://phdru.name/            ph...@ph...
>           Programmers don't die, they just GOSUB without RETURN.
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>

Re: [SQLObject] SqlObject Sqlmeta fromDatabase problem

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

On Mon, Mar 26, 2012 at 07:59:39AM -0500, Jeremy Hoyle wrote:
>   File "C:\Pysoft\Software\SMS Development\tests\test0.py", line 5, in
> <module>
>     from pySMS import Companys
>   File "C:\Pysoft\Software\SMS Development\pySMS\__init__.py", line 1, in
> <module>
>     from Company import Companys

   Here is the problem now - Company (and Companys) is imported before
a connection is created. You have to open a connection before the class
Company is created (i.e., before the module is imported).

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

Re: [SQLObject] SqlObject Sqlmeta fromDatabase problem

[Jeremy H. <jer...@gm...>]

Yes. If I remove Companys as a SQLObject.I still receive the same error.
I'm not sure from the sequence of the ( from Company import Companys ) is
trying to initiate (  class Company(SQLObject) ) class.

class Companys():
    def __init__(self):
       connection_string = 'mysql://root:ttlan1@127.0.0.1:3306/pySMS'
       conn = connectionForURI(connection_string,debug = True,autoCommit =
True)
       trans = conn.transaction()
       sqlhub.processConnection = conn
       Company.createTable(ifNotExists = True, connection=trans)

Traceback (most recent call last):
  File "C:\Pysoft\Software\SMS Development\tests\test0.py", line 5, in
<module>
    from pySMS import Companys
  File "C:\Pysoft\Software\SMS Development\pySMS\__init__.py", line 1, in
<module>
    from Company import Companys
  File "C:\Pysoft\Software\SMS Development\pySMS\Company.py", line 137, in
<module>
    class Company(SQLObject):
  File
"C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\declarative.py",
line 92, in __new__
    cls.__classinit__(cls, new_attrs)
  File
"C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\main.py",
line 789, in __classinit__
    sqlmeta.addColumnsFromDatabase()
  File
"C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\main.py",
line 441, in addColumnsFromDatabase
    conn = connection or soClass._connection
  File
"C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\dbconnection.py",
line 902, in __get__
    return self.getConnection()
  File
"C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\dbconnection.py",
line 915, in getConnection
    "No connection has been defined for this thread "
AttributeError: No connection has been defined for this thread or process

On Mon, Mar 26, 2012 at 7:47 AM, Oleg Broytman <ph...@ph...> wrote:

> On Mon, Mar 26, 2012 at 07:42:40AM -0500, Jeremy Hoyle wrote:
> > *Companys is not a sqlobject table. Company is a sqlobject table.
> >
> > class Companys(SQLObject):
>
>   I clearly see here that Companys is an SQLObject and hence require a
> connection.
>
> Oleg.
> --
>     Oleg Broytman            http://phdru.name/            ph...@ph...
>           Programmers don't die, they just GOSUB without RETURN.
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>

Re: [SQLObject] SqlObject Sqlmeta fromDatabase problem

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

On Mon, Mar 26, 2012 at 07:42:40AM -0500, Jeremy Hoyle wrote:
> *Companys is not a sqlobject table. Company is a sqlobject table.
> 
> class Companys(SQLObject):

   I clearly see here that Companys is an SQLObject and hence require a
connection.

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

Re: [SQLObject] SqlObject Sqlmeta fromDatabase problem

[Jeremy H. <jer...@gm...>]

 What's that? A global function or a method? Where it's called?
*It is the Companys class. It is called from my test0.py file. See below.*
*
*
 The same problem - no connection has been defined. The code tried to
open a connection in Companys.__init__, but Companys is an SQLObject's
table and thus requires an open connection.
 Open a connection outside of SQLObject's initialization.

*Companys is not a sqlobject table. Company is a sqlobject table. Sorry for
the confusion. I chose poor naming. Do I not need to extend the SQLObject
in Companys? See all of them below.*

*Company.py file *
class Company(SQLObject):
    class sqlmeta:
       fromDatabase = True
       lazyUpdate = True
       cacheValues = True
   Company_Name = StringCol(length = 256, default = None)
   Company_Address = StringCol(length = 256, default = None)
   Company_Phone = StringCol(length = 256, default = None)

class Companys(SQLObject):
     def __init__(self):
         connection_string = 'mysql://user:password@127.0.0.1:3306/pySMS'
         conn = connectionForURI(connection_string,debug = True,autoCommit
=True)
         trans = conn.transaction()
         sqlhub.processConnection = conn
         Company.createTable(ifNotExists = True, connection=trans)

 *test0.py file*

 import sys
 from sqlobject import *
 from pySMS import Companys

 if __name__ == "__main__":

     pysoft = Companys()

On Mon, Mar 26, 2012 at 4:42 AM, Oleg Broytman <ph...@ph...> wrote:

> On Mon, Mar 26, 2012 at 04:30:26AM -0500, Jeremy Hoyle wrote:
> > Thank you for your response. I'm sorry for not including these details
> for
> > I have been struggling with this problem for sometime. These suggestions
> > have been tried or already implemented with the same result. Pleased let
> me
> > know if you have any other suggestions.
> >
> > def __init__(self):
> >     connection_string = 'mysql://user:password@127.0.0.1:3306/pySMS'
> >     conn = connectionForURI(connection_string,debug = True,autoCommit =
> > True)
> >     trans = conn.transaction()
> >     sqlhub.processConnection = conn
> >     Company.createTable(ifNotExists = True, connection=trans)
>
>    What's that? A global function or a method? Where it's called?
>
> > test0.py file
> >
> > import sys
> > from sqlobject import *
> > from pySMS import Companys
> >
> > if __name__ == "__main__":
> >
> >     pysoft = Companys()
> >
> >
> > Traceback (most recent call last):
> >   File "C:\Pysoft\Software\SMS Development\tests\test0.py", line 5, in
> > <module>
> >     from pySMS import Companys
> >   File "C:\Pysoft\Software\SMS Development\pySMS\__init__.py", line 1, in
> > <module>
> >     from Company import Companys
> >   File "C:\Pysoft\Software\SMS Development\pySMS\Company.py", line 137,
> in
> > <module>
> >     class Company(SQLObject):
> >   File
> >
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\declarative.py",
> > line 92, in __new__
> >     cls.__classinit__(cls, new_attrs)
> >   File
> >
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\main.py",
> > line 789, in __classinit__
> >     sqlmeta.addColumnsFromDatabase()
> >   File
> >
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\main.py",
> > line 441, in addColumnsFromDatabase
> >     conn = connection or soClass._connection
> >   File
> >
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\dbconnection.py",
> > line 902, in __get__
> >     return self.getConnection()
> >   File
> >
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\dbconnection.py",
> > line 915, in getConnection
> >     "No connection has been defined for this thread "
> > AttributeError: No connection has been defined for this thread or process
>
>    The same problem - no connection has been defined. The code tried to
> open a connection in Companys.__init__, but Companys is an SQLObject's
> table and thus requires an open connection.
>   Open a connection outside of SQLObject's initialization.
>
> Oleg.
> --
>     Oleg Broytman            http://phdru.name/            ph...@ph...
>           Programmers don't die, they just GOSUB without RETURN.
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>

Re: [SQLObject] SqlObject Sqlmeta fromDatabase problem

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

On Mon, Mar 26, 2012 at 04:30:26AM -0500, Jeremy Hoyle wrote:
> Thank you for your response. I'm sorry for not including these details for
> I have been struggling with this problem for sometime. These suggestions
> have been tried or already implemented with the same result. Pleased let me
> know if you have any other suggestions.
> 
> def __init__(self):
>     connection_string = 'mysql://user:password@127.0.0.1:3306/pySMS'
>     conn = connectionForURI(connection_string,debug = True,autoCommit =
> True)
>     trans = conn.transaction()
>     sqlhub.processConnection = conn
>     Company.createTable(ifNotExists = True, connection=trans)

   What's that? A global function or a method? Where it's called?

> test0.py file
> 
> import sys
> from sqlobject import *
> from pySMS import Companys
> 
> if __name__ == "__main__":
> 
>     pysoft = Companys()
> 
> 
> Traceback (most recent call last):
>   File "C:\Pysoft\Software\SMS Development\tests\test0.py", line 5, in
> <module>
>     from pySMS import Companys
>   File "C:\Pysoft\Software\SMS Development\pySMS\__init__.py", line 1, in
> <module>
>     from Company import Companys
>   File "C:\Pysoft\Software\SMS Development\pySMS\Company.py", line 137, in
> <module>
>     class Company(SQLObject):
>   File
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\declarative.py",
> line 92, in __new__
>     cls.__classinit__(cls, new_attrs)
>   File
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\main.py",
> line 789, in __classinit__
>     sqlmeta.addColumnsFromDatabase()
>   File
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\main.py",
> line 441, in addColumnsFromDatabase
>     conn = connection or soClass._connection
>   File
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\dbconnection.py",
> line 902, in __get__
>     return self.getConnection()
>   File
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\dbconnection.py",
> line 915, in getConnection
>     "No connection has been defined for this thread "
> AttributeError: No connection has been defined for this thread or process

   The same problem - no connection has been defined. The code tried to
open a connection in Companys.__init__, but Companys is an SQLObject's
table and thus requires an open connection.
   Open a connection outside of SQLObject's initialization.

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

Re: [SQLObject] SqlObject Sqlmeta fromDatabase problem

[Jeremy H. <jer...@gm...>]

Thank you for your response. I'm sorry for not including these details for
I have been struggling with this problem for sometime. These suggestions
have been tried or already implemented with the same result. Pleased let me
know if you have any other suggestions.

def __init__(self):
    connection_string = 'mysql://user:password@127.0.0.1:3306/pySMS'
    conn = connectionForURI(connection_string,debug = True,autoCommit =
True)
    trans = conn.transaction()
    sqlhub.processConnection = conn
    Company.createTable(ifNotExists = True, connection=trans)

test0.py file

import sys
from sqlobject import *
from pySMS import Companys

if __name__ == "__main__":

    pysoft = Companys()


Traceback (most recent call last):
  File "C:\Pysoft\Software\SMS Development\tests\test0.py", line 5, in
<module>
    from pySMS import Companys
  File "C:\Pysoft\Software\SMS Development\pySMS\__init__.py", line 1, in
<module>
    from Company import Companys
  File "C:\Pysoft\Software\SMS Development\pySMS\Company.py", line 137, in
<module>
    class Company(SQLObject):
  File
"C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\declarative.py",
line 92, in __new__
    cls.__classinit__(cls, new_attrs)
  File
"C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\main.py",
line 789, in __classinit__
    sqlmeta.addColumnsFromDatabase()
  File
"C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\main.py",
line 441, in addColumnsFromDatabase
    conn = connection or soClass._connection
  File
"C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\dbconnection.py",
line 902, in __get__
    return self.getConnection()
  File
"C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\dbconnection.py",
line 915, in getConnection
    "No connection has been defined for this thread "
AttributeError: No connection has been defined for this thread or process



On Mon, Mar 26, 2012 at 3:52 AM, Oleg Broytman <ph...@ph...> wrote:

> Hi!
>
> On Sun, Mar 25, 2012 at 06:56:32PM -0500, Jeremy Hoyle wrote:
> > I have a problem while trying to use the "fromDatabase = True" option in
> > sqlmeta. Any time I enable this. it gives me the connection error below.
> Is
> > there another attribute I need to do before doing this? I saw another
> > thread with this problem but the solution was enable the connection
> before
> > the class which I have done.
> >
> > from sqlobject import *
> >
> > class Companys(SQLObject):
> >      def __init__(self):
> >         connection_string = 'mysql://user:password@127.0.0.1:3306/pySMS'
> >         conn = connectionForURI(connection_string,debug =
> True,autoCommit =
> > True)
> >         trans = conn.transaction()
> >         sqlhub.processConnection = conn
> >         Company.createTable(ifNotExists = True, connection=conn)
> >         Company._connection.debug = True
>
>    A number of problems here.
> 1. The connection is created in Companys.__init__ which is not called,
> at least it is not called when SQLObject's metaclass processes
> fromDatabase. fromDatabase requires an open connection.
> 2. A transaction is opened but never used. Transaction (trans, in your
> case) has to be used instead of connection (in sqlhub, or in every
> SQLObject call that accepts connection).
>
> > class Company(SQLObject):
> >
> >     class sqlmeta:
> >        fromDatabase = True
> >        lazyUpdate = True
> >        cacheValues = True
> >
> >     Company_Name = StringCol(length = 256, default = None)
> >     Company_Address = StringCol(length = 256, default = None)
> >     Company_Phone = StringCol(length = 256, default = None)
> >
> > Traceback (most recent call last):
> >   File "C:\Pysoft\Software\SMS Development\tests\test0.py", line 5, in
> > <module>
> >     from pySMS import Companys
> >   File "C:\Pysoft\Software\SMS Development\pySMS\__init__.py", line 1, in
> > <module>
> >     from Company import Companys
> >   File "C:\Pysoft\Software\SMS Development\pySMS\Company.py", line 138,
> in
> > <module>
> >     class Company(SQLObject):
> >   File
> >
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\declarative.py",
> > line 92, in __new__
> >     cls.__classinit__(cls, new_attrs)
> >   File
> >
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\main.py",
> > line 789, in __classinit__
> >     sqlmeta.addColumnsFromDatabase()
> >   File
> >
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\main.py",
> > line 441, in addColumnsFromDatabase
> >     conn = connection or soClass._connection
> >   File
> >
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\dbconnection.py",
> > line 902, in __get__
> >     return self.getConnection()
> >   File
> >
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\dbconnection.py",
> > line 915, in getConnection
> >     "No connection has been defined for this thread "
> > AttributeError: No connection has been defined for this thread or process
>
> Oleg.
> --
>     Oleg Broytman            http://phdru.name/            ph...@ph...
>           Programmers don't die, they just GOSUB without RETURN.
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>

Re: [SQLObject] SqlObject Sqlmeta fromDatabase problem

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

Hi!

On Sun, Mar 25, 2012 at 06:56:32PM -0500, Jeremy Hoyle wrote:
> I have a problem while trying to use the "fromDatabase = True" option in
> sqlmeta. Any time I enable this. it gives me the connection error below. Is
> there another attribute I need to do before doing this? I saw another
> thread with this problem but the solution was enable the connection before
> the class which I have done.
> 
> from sqlobject import *
> 
> class Companys(SQLObject):
>      def __init__(self):
>         connection_string = 'mysql://user:password@127.0.0.1:3306/pySMS'
>         conn = connectionForURI(connection_string,debug = True,autoCommit =
> True)
>         trans = conn.transaction()
>         sqlhub.processConnection = conn
>         Company.createTable(ifNotExists = True, connection=conn)
>         Company._connection.debug = True

   A number of problems here.
1. The connection is created in Companys.__init__ which is not called,
at least it is not called when SQLObject's metaclass processes
fromDatabase. fromDatabase requires an open connection.
2. A transaction is opened but never used. Transaction (trans, in your
case) has to be used instead of connection (in sqlhub, or in every
SQLObject call that accepts connection).

> class Company(SQLObject):
> 
>     class sqlmeta:
>        fromDatabase = True
>        lazyUpdate = True
>        cacheValues = True
> 
>     Company_Name = StringCol(length = 256, default = None)
>     Company_Address = StringCol(length = 256, default = None)
>     Company_Phone = StringCol(length = 256, default = None)
> 
> Traceback (most recent call last):
>   File "C:\Pysoft\Software\SMS Development\tests\test0.py", line 5, in
> <module>
>     from pySMS import Companys
>   File "C:\Pysoft\Software\SMS Development\pySMS\__init__.py", line 1, in
> <module>
>     from Company import Companys
>   File "C:\Pysoft\Software\SMS Development\pySMS\Company.py", line 138, in
> <module>
>     class Company(SQLObject):
>   File
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\declarative.py",
> line 92, in __new__
>     cls.__classinit__(cls, new_attrs)
>   File
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\main.py",
> line 789, in __classinit__
>     sqlmeta.addColumnsFromDatabase()
>   File
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\main.py",
> line 441, in addColumnsFromDatabase
>     conn = connection or soClass._connection
>   File
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\dbconnection.py",
> line 902, in __get__
>     return self.getConnection()
>   File
> "C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\dbconnection.py",
> line 915, in getConnection
>     "No connection has been defined for this thread "
> AttributeError: No connection has been defined for this thread or process

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

[SQLObject] SqlObject Sqlmeta fromDatabase problem

[Jeremy H. <jer...@gm...>]

I have a problem while trying to use the "fromDatabase = True" option in
sqlmeta. Any time I enable this. it gives me the connection error below. Is
there another attribute I need to do before doing this? I saw another
thread with this problem but the solution was enable the connection before
the class which I have done.

from sqlobject import *

class Companys(SQLObject):
     def __init__(self):
        connection_string = 'mysql://user:password@127.0.0.1:3306/pySMS'
        conn = connectionForURI(connection_string,debug = True,autoCommit =
True)
        trans = conn.transaction()
        sqlhub.processConnection = conn
        Company.createTable(ifNotExists = True, connection=conn)
        Company._connection.debug = True

class Company(SQLObject):

    class sqlmeta:
       fromDatabase = True
       lazyUpdate = True
       cacheValues = True

    Company_Name = StringCol(length = 256, default = None)
    Company_Address = StringCol(length = 256, default = None)
    Company_Phone = StringCol(length = 256, default = None)

Traceback (most recent call last):
  File "C:\Pysoft\Software\SMS Development\tests\test0.py", line 5, in
<module>
    from pySMS import Companys
  File "C:\Pysoft\Software\SMS Development\pySMS\__init__.py", line 1, in
<module>
    from Company import Companys
  File "C:\Pysoft\Software\SMS Development\pySMS\Company.py", line 138, in
<module>
    class Company(SQLObject):
  File
"C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\declarative.py",
line 92, in __new__
    cls.__classinit__(cls, new_attrs)
  File
"C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\main.py",
line 789, in __classinit__
    sqlmeta.addColumnsFromDatabase()
  File
"C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\main.py",
line 441, in addColumnsFromDatabase
    conn = connection or soClass._connection
  File
"C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\dbconnection.py",
line 902, in __get__
    return self.getConnection()
  File
"C:\Python27\lib\site-packages\sqlobject-1.2.1-py2.7.egg\sqlobject\dbconnection.py",
line 915, in getConnection
    "No connection has been defined for this thread "
AttributeError: No connection has been defined for this thread or process

Re: [SQLObject] The autocommit bug with psycopg2

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

>    Archives are listed at http://sqlobject.org/community.html

Indeed.  Sorry.  I misread that sentence and thought it referred
to a different list.  Silly me.

>    The bug has been fixed in SQLObject 1.2. Consider upgrading to a
> later version.

Brilliant.  Thank you very much.
It is either that, or just pray patiently that
Ubuntu will upgrade it in the next release next month :-)

:-- George

Re: [SQLObject] The autocommit bug with psycopg2

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

On Sun, Mar 18, 2012 at 06:50:07PM +0100, Hans Georg Schaathun wrote:
> sorry if this is an old topic, but I did not find any list
> archive.

   Archives are listed at http://sqlobject.org/community.html

> I just took up using SQLObject a few weeks ago;
> very convenient.
> 
>   File
> "/usr/lib/pymodules/python2.7/sqlobject/postgres/pgconnection.py", line
> 133, in makeConnection
>     conn.autocommit(1)
> TypeError: 'bool' object is not callable

   The bug has been fixed in SQLObject 1.2. Consider upgrading to a
later version.

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

[SQLObject] The autocommit bug with psycopg2

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

Hi,

sorry if this is an old topic, but I did not find any list
archive.  I just took up using SQLObject a few weeks ago;
very convenient.

I wonder if anyone has experience with a bug where the
the postgress connection attempts to call a boolean
value (autocommit) as a method.  (Call stack is cut in below.)
It is not a new problem, I found it reported here as well:
http://stackoverflow.com/questions/6374121/python-why-does-sqlobject-fail-in-conn-autocommit1

What is odd is that my code works fine on Ubuntu 10.4 with a connection
to localhost.  When I run the same code on Ubuntu 10.10 with a remote
server, it fails.  I am not sure if the difference is with the
remoteness or the software version ... So far I have tried to make do
 with the standard ubuntu packages for sqlobject and postgres.

Does anyone know if this problem has been resolved in some recent 
version of sqlobject/psycopg?  Or if there is a known workaround?
I do observe that the URL below suggests what looks like a 
downgrading of psycopg2, which I won't do if upgrading is an option :-)

My call stack is:
  File "/home/georg/git/pysteg/src/pysteg/sql/tables.py", line 346, in
getJob
    trans = conn.transaction()
  File "/usr/lib/pymodules/python2.7/sqlobject/dbconnection.py", line
400, in transaction
    return Transaction(self)
  File "/usr/lib/pymodules/python2.7/sqlobject/dbconnection.py", line
686, in __init__
    self._connection = dbConnection.getConnection()
  File "/usr/lib/pymodules/python2.7/sqlobject/dbconnection.py", line
271, in getConnection
    conn = self.makeConnection()
  File
"/usr/lib/pymodules/python2.7/sqlobject/postgres/pgconnection.py", line
133, in makeConnection
    conn.autocommit(1)
TypeError: 'bool' object is not callable

Thanks a lot in advance,
:-- George

[SQLObject] SQLObject 1.2.2

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

Hello!

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


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

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

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


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

Site:
http://sqlobject.org

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

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

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

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

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


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

* A bug was fixed in SQLiteConnection - clear _threadPool on close().

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

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

[SQLObject] SQLObject 1.1.5

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

Hello!

I'm pleased to announce version 1.1.5, a bugfix release of branch
1.1 of SQLObject.


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

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

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


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

Site:
http://sqlobject.org

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

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

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

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

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


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

* A bug was fixed in SQLiteConnection - clear _threadPool on close().

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] Unicode probs...

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

On Tue, Feb 28, 2012 at 01:56:50PM -0500, Markos Kapes wrote:
> 	Out[21]: Title is: title names are:  [u'publisher', u'isbn', 'kind_id', 'booktitle', u'release_date', u'edition', u'tag', u'type']  values are: [' ', ' ', 1, '\xc3\xa9tape', None, None, None, None]
> So, yes, there are unicode strings in the names.

   To fix that edit sqlobject/mysql/mysqlconnection.py, method
columnsFromSchema; search for assignments

kw['name'] = soClass.sqlmeta.style.dbColumnToPythonAttr(field)
kw['dbName'] = field

   make them strings:

kw['name'] = str(soClass.sqlmeta.style.dbColumnToPythonAttr(field))
kw['dbName'] = str(field)

   test and report if that helps.

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

Re: [SQLObject] (no subject)

[Markos K. <mk...@gm...>]

Here's the result:
	In[21]: Title(booktitle=u'étape', kindID=1)
	Out[21]: Title is: title names are:  [u'publisher', u'isbn', 'kind_id', 'booktitle', u'release_date', u'edition', u'tag', u'type']  values are: [' ', ' ', 1, '\xc3\xa9tape', None, None, None, None]
So, yes, there are unicode strings in the names. Oddly enough, the only ones that are unicode are the ones that are fromTable (booktitle is the only declared UnicodeCol & kindID is a foreign key)
Now, the weird part is that when I add an ascii compatible string, despite the fact that some of the  names are still unicode, it all works and I get a sqlobject entered in the database:
	In[22]: Title(booktitle=u'tape', kindID=1)
	Out[22]: title [u'publisher', u'isbn', 'kind_id', 'booktitle', u'release_date', u'edition', u'tag', u'type'] [' ', ' ', 1, 'tape', None, None, None, None]
	<Title 11275L booktitle=u'tape' kindID=1L isbn=u' ' publisher=u' ' releaseDate=None tag=None edition=None type=None>

Thanks, Oleg,  unicode errors still always manage to confuse the hell out of me...
--Marko

On Mon, 2012-02-28 09:11, Oleg Broytman wrote:
> On Mon, Feb 27, 2012 at 08:20:57PM -0500, Markos Kapes wrote:
> > I"m getting a UnicodeDecodeError and I"m unsure how to fix it...
> > 	/Library/Python/2.7/site-packages/sqlobject/dbconnection.pyc in _insertSQL(self, table, names, values)
> >     	460         return ("INSERT INTO %s (%s) VALUES (%s)" %
> >     	461                 (table, ', '.join(names),
> >     --> 462                  ', '.join([self.sqlrepr(v) for v in values])))
> >     	463 
> >     	464     def transaction(self):
> > 
> > 	UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 14: ordinal not in range(128)
> > I'm using sqlobject 1.2.1, mysqldb 1.2.3 and the tables in the database are formatted for unicode. The objects' columns in sql are UnicodeCol. The connection string for the database is 
> > 	u'
> mysql://dbuser:@localhost/databasename?debug=1&logger=MyLogger&loglevel=debug&use_unicode=1&charset=utf8
> '
> > Not sure what else to try....
> 
>    Can you test if there are unicode names in the ``names`` list?
> 
> Oleg.
> -- 
>      Oleg Broytman            
> http://phdru.name/
>             phd@...
>            Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Unicode probs...

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

On Mon, Feb 27, 2012 at 08:20:57PM -0500, Markos Kapes wrote:
> I"m getting a UnicodeDecodeError and I"m unsure how to fix it...
> 	/Library/Python/2.7/site-packages/sqlobject/dbconnection.pyc in _insertSQL(self, table, names, values)
>     	460         return ("INSERT INTO %s (%s) VALUES (%s)" %
>     	461                 (table, ', '.join(names),
>     --> 462                  ', '.join([self.sqlrepr(v) for v in values])))
>     	463 
>     	464     def transaction(self):
> 
> 	UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 14: ordinal not in range(128)
> I'm using sqlobject 1.2.1, mysqldb 1.2.3 and the tables in the database are formatted for unicode. The objects' columns in sql are UnicodeCol. The connection string for the database is 
> 	u'mysql://dbuser:@localhost/databasename?debug=1&logger=MyLogger&loglevel=debug&use_unicode=1&charset=utf8'
> Not sure what else to try....

   Can you test if there are unicode names in the ``names`` list?

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

[SQLObject] Unicode probs...

[Markos K. <mk...@gm...>]

I"m getting a UnicodeDecodeError and I"m unsure how to fix it...
	/Library/Python/2.7/site-packages/sqlobject/dbconnection.pyc in _insertSQL(self, table, names, values)
    	460         return ("INSERT INTO %s (%s) VALUES (%s)" %
    	461                 (table, ', '.join(names),
    --> 462                  ', '.join([self.sqlrepr(v) for v in values])))
    	463 
    	464     def transaction(self):

	UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 14: ordinal not in range(128)
I'm using sqlobject 1.2.1, mysqldb 1.2.3 and the tables in the database are formatted for unicode. The objects' columns in sql are UnicodeCol. The connection string for the database is 
	u'mysql://dbuser:@localhost/databasename?debug=1&logger=MyLogger&loglevel=debug&use_unicode=1&charset=utf8'
Not sure what else to try....

Thanks for any help.....
--marko