sqlobject-discuss — All things SQLObject-related

Re: [SQLObject] mysql connection losses

[Ian B. <ia...@co...>]

On Mar 17, 2004, at 8:18 PM, David Warnock wrote:
> Our Java connection pool tests every connection before it gives it to 
> the client (by setting autocommit). If the test fails then the 
> connection is removed from the pool and the next connection (or if 
> required a new connection) is returned.
>
> We added this because both MySQL and MS SQL Server seemed to not like 
> having connections around for long periods of time and would close 
> them at inopportune times.
>
> Maybe SQL Object could do something similar.

It would be easy to add *if* there's an interface to do this with the 
database driver.  If there was, DBAPIConnection.getConnection() could 
ping the database before returning the connection.

--
Ian Bicking | ia...@co... | http://blog.ianbicking.org

Re: [SQLObject] mysql connection losses

[David W. <da...@su...>]

Victor,

> I'm getting the following error in my application using SQLObject 0.5.1 
> and MySQL.
> 
> Any ideas on how to work around this problem?  I'd like to be able to 
> set an expiry option on the connection pool so that connections will 
> only be used 'N' number of times before they get closed and discarded.

Our Java connection pool tests every connection before it gives it to 
the client (by setting autocommit). If the test fails then the 
connection is removed from the pool and the next connection (or if 
required a new connection) is returned.

We added this because both MySQL and MS SQL Server seemed to not like 
having connections around for long periods of time and would close them 
at inopportune times.

Maybe SQL Object could do something similar.

Regards

Dave
-- 
David Warnock, Sundayta Ltd. http://www.sundayta.com
iDocSys for Document Management. VisibleResults for Fundraising.
Development and Hosting of Web Applications and Sites.

Re: [sqlobject] Re: [SQLObject] mysql connection losses

[Victor Ng <vn...@sy...>]

Grrr....

This is really annoying.

I'm using MySQL for this one database because Postgresql seems to have 
broken the error handling between 7.2 and 7.4.  I've got 7.2 on my 
production server and 7.4 on my laptop right now.  Trying to connect 
with psycopg on a 7.4 client to a 7.4 server doesn't work properly so I 
can't connect to Postgres from my laptop which is running pgsql 7.4.

I can only connect remotely to the Postgres 7.2 database using a lone 
Linux machine sitting in the corner of the room.

I've tried switching to a Unix Domain socket from a TCP connection in 
MySQLdb and I still get errors (different errors - but errors 
nonetheless).

I hate MySQL.   Gah.  Thanks for the help - at least I don't feel 
completely stupid.  I'll be switching back to Postgresql.

vic

On Mar 17, 2004, at 3:01 PM, Frank Barknecht wrote:

> Hallo,
> Victor Ng hat gesagt: // Victor Ng wrote:
>
>> I'm getting the following error in my application using SQLObject 
>> 0.5.1
>> and MySQL.
>>
>> Any ideas on how to work around this problem?
>
> Install and use PostgreSQL.
>
> Sorry to say this, but at least I was fighting and googling this
> problem for weeks to no avail at all, I tried various patches to
> python-mysql, nothing helped. As my project was nearing release time,
> I switched to PostgreSQL the night before deadline which finally fixed
> all my problems. I don't know who to blame, but I don't blame me
> anymore. ;)
>
> No I can do python progamming again instead of struggling with a (to
> me) unsolvable problem.
>
> ciao
> -- 
>  Frank Barknecht                               _ ______footils.org__
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>
>
---
"We are what we repeatedly do. Excellence then, is not an act. It is a 
habit."  - Aristotle

Re: [SQLObject] mysql connection losses

[Frank B. <fb...@fo...>]

Hallo,
Victor Ng hat gesagt: // Victor Ng wrote:

> I'm getting the following error in my application using SQLObject 0.5.1 
> and MySQL.
> 
> Any ideas on how to work around this problem?  

Install and use PostgreSQL. 

Sorry to say this, but at least I was fighting and googling this
problem for weeks to no avail at all, I tried various patches to
python-mysql, nothing helped. As my project was nearing release time,
I switched to PostgreSQL the night before deadline which finally fixed
all my problems. I don't know who to blame, but I don't blame me
anymore. ;)

No I can do python progamming again instead of struggling with a (to
me) unsolvable problem.

ciao
-- 
 Frank Barknecht                               _ ______footils.org__

[SQLObject] mysql connection losses

[Victor Ng <vn...@ma...>]

I'm getting the following error in my application using SQLObject 0.5.1 
and MySQL.

Any ideas on how to work around this problem?  I'd like to be able to 
set an expiry option on the connection pool so that connections will 
only be used 'N' number of times before they get closed and discarded.

   16912   File 
"/usr/local/lib/python2.3/site-packages/SQLObject/Join.py", line 104, 
in performJoin
   16913     inst.id)
   16914   File 
"/usr/local/lib/python2.3/site-packages/SQLObject/DBConnection.py", 
line 328, in _SO_selectJoin
   16915     return self.queryAll("SELECT %s FROM %s WHERE %s = %s" %
   16916   File 
"/usr/local/lib/python2.3/site-packages/SQLObject/DBConnection.py", 
line 136, in queryAll
   16917     return self._runWithConnection(self._queryAll, s)
   16918   File 
"/usr/local/lib/python2.3/site-packages/SQLObject/DBConnection.py", 
line 72, in _runWithConnection
   16919     val = meth(conn, *args)
   16920   File 
"/usr/local/lib/python2.3/site-packages/SQLObject/DBConnection.py", 
line 129, in _queryAll
   16921     c.execute(s)
   16922   File 
"/usr/local/lib/python2.3/site-packages/MySQLdb/cursors.py", line 61, 
in execute
   16923     r = self._query(query)  16924   File 
"/usr/local/lib/python2.3/site-packages/MySQLdb/cursors.py", line 168, 
in _query  16925     rowcount = self._BaseCursor__do_query(q)
   16926   File 
"/usr/local/lib/python2.3/site-packages/MySQLdb/cursors.py", line 112, 
in __do_query
   16927     db.query(q)
   16928 OperationalError: (2013, 'Lost connection to MySQL server 
during query')

[SQLObject] connections redux

[Ben <be...@me...>]

RE: my connection pool increasing (SQLObject 0.5.2, FreeBSD, psychopg
/ Postgres):

i've isolated where the connection numbers are increasing:

self.itemcls.select(orderBy=self.orderBySQL)[start:start+self.pa\
geLen]

i found this in the release notes:

Using .select() would hold on to a connection, and also release it
back to the connection pool. Very un-threadsafe and all-around bad.

is this bug still in existence?

how do i select limit / offset without keeping allocating a
connection?

thanks, Ben Lee

[SQLObject] connections, threads, processes

[Ben <be...@me...>]

sorry in advance i'm a sqlobject newbie.

i'm using sqlobject 0.5.2 in mod_python + apache / freebsd with
psycopg + postgres.  as it is a long living server with a lot of
processes, i need to keep the connection count down to avoid running
out of connections.

since i'm on freebsd and apache threads don't work there, i'm using
the prefork model, so each child process is single-threaded.  now,
correct me if i'm wrong, but AFAICT this means that i should never
need more than one connect per child.  however i log

os.getpid + DBConnection._connectionCount

and i see the number growing inside the processes.  this is troubling.
i know SQLObject is doing connection pooling, but since it's single
threaded, why is this pool growing?  in fact psycopg CURSORS can be
shared between threads, so we shouldn't even need more than one of
those, right?

help!

thanks, Ben Lee

Re: [SQLObject] fetch instance using column other than ID

[charles b. <li...@st...>]

Thank you Luke and Ian!  alternateID was exactly what I was looking for.  It
always seems so obvious after the fact.  :) Would it make sense to mention
it earlier in the docs when talking about fetching instances that already
exist?  Something like the following maybe?

"You can use the class method .get() to fetch instances that already exist.
So if you wanted to fetch the Person by id 10, you'd call Person.get(10).
To fetch using data from other unique columns, specify alternateID=True in
that column's initialization and use the class method .by<ColumnName>().
(see alternateID for more detail)"

Ian's lookup class example was also what I had in mind. I think there was
one minor typo in the select that I fixed below, incase others try that.
>
> class Person(SQLObject):
>      def lookup(cls, email, connection=None):
>          return cls.select(cls.q.email=email, connection=connection)[0]
>      lookup = classmethod(lookup)
>

I need to read up on new class styles now..  :)  Thanks for the pointers...

-Charles.

Re: [SQLObject] fetch instance using column other than ID

[Luke O. <lu...@me...>]

Sounds like you might be looking for the alternateID=True argument for columns:

  email = StringCol(alternateID=True)

will add an access method to Person so that:

user = Person.byEmail('ab...@xy...')

will work.

- Luke

Quoting charles brandt <li...@st...>:
> user = Person.select(Person.q.email=="ab...@xy...", connection=req.conn)[0]
>
> but that seems rather unintuitive compared to Person(10) (or Person.get(10)
> now).  

Re: [SQLObject] fetch instance using column other than ID

[Ian B. <ia...@co...>]

On Mar 11, 2004, at 1:19 AM, charles brandt wrote:
> Sorry for the newbie question, but I'm having a hard time finding the 
> right
> way to fetch an existing class instance using a different column than 
> id.
> Assuming the example Person class with an added "email = StringCol()", 
> I am
> able to fetch based on the email using something like:
>
> user = Person.select(Person.q.email=="ab...@xy...", 
> connection=req.conn)[0]
>
> but that seems rather unintuitive compared to Person(10) (or 
> Person.get(10)
> now).  I think I'm envisioning an overridden _init  but the magic of 
> the
> metaclass is confusing me on how to implement it.  I was also thinking
> something along the lines of a class function (ie
> user=Person.lookup("ab...@xy...", req.conn) ) would be nice, but since 
> it is
> actually being initialized I don't think this is correct.
>
> Any ideas/comments?  Thanks in advance...

class Person(SQLObject):
     email = StringCol(alternateID=True)

user = Person.byEmail("ab...@xy...")

Or just:

user = Person.select(email="ab...@xy...")[0]

Or:

class Person(SQLObject):
     def lookup(cls, email, connection=None):
         return cls.select(email=email, connection=connection)[0]
     lookup = classmethod(lookup)

--
Ian Bicking | ia...@co... | http://blog.ianbicking.org

[SQLObject] fetch instance using column other than ID

[charles b. <li...@st...>]

Hi List,

Sorry for the newbie question, but I'm having a hard time finding the right
way to fetch an existing class instance using a different column than id.
Assuming the example Person class with an added "email = StringCol()", I am
able to fetch based on the email using something like:

user = Person.select(Person.q.email=="ab...@xy...", connection=req.conn)[0]

but that seems rather unintuitive compared to Person(10) (or Person.get(10)
now).  I think I'm envisioning an overridden _init  but the magic of the
metaclass is confusing me on how to implement it.  I was also thinking
something along the lines of a class function (ie
user=Person.lookup("ab...@xy...", req.conn) ) would be nice, but since it is
actually being initialized I don't think this is correct.

Any ideas/comments?  Thanks in advance...

-Charles.

[SQLObject] Re: Inserting Boolean Columns Into PostgreSQL - Again

[Chris G. <ch...@il...>]

"CLIFFORD ILKAY" <cli...@di...> wrote in message
news:5.2.0.9.0.20040310151025.04674140@localhost...
> If the order of the columns is not as one would expect, that would wreck
> INSERT statements that rely on the position of columns rather than the
> absolute name of the columns. This is probably not a problem in SQLObject
> but it could be if one uses other tools to manipulate the same database.

Eeeew.. there are tools that use the column number rather than the name?!
What a horrible coding practice.

Re: [SQLObject] Re: Inserting Boolean Columns Into PostgreSQL - Again

[CLIFFORD I. <cli...@di...>]

At 06:14 10/03/2004 -0500, Chris Gahan wrote:
>Ian answered your first question, so I'll field the second one. :)
>
>"Clifford Ilkay" <cli...@di...> wrote in message
>news:200403091343.17553.clifford_ilkay at dinamis.com...
> > testdb=# select * from person;
> >  id | last_name | is_member | first_name
> > ----+-----------+-----------+------------
> >   1 | Duck      | t         | Donald
> >   2 | Mouse     | t         | Mickey
> >   3 | Mouse     | t         | Minnie
> >   4 | Dog       | t         | Pluto
> >   5 | Dog       | t         | Goofy
> > (5 rows)
> >
> > As you can see, I tried various ways of expressing "False" but none of
>them
> > seemed to work. What am I missing? Also, why is the order of the columns
>not
> > the same as the order that was specified in the class definition?
>
>I haven't looked this up, but this is probably what's happening:
>
>When you create a subclass of an SQLObject, you're creating a new python
>object. To create the table, SQLObject has to inspect this python object's
>attributes to see which of them are Col() classes. Now, internally, python
>stores all the attributes of a class in a dict(), so that when you look up
>an attribute, it just does a lookup in the dict(). The reason they're out of
>order is that dictionaries don't maintain any kind of order. The order of
>the things in a dictionary depends on the order you inserted them. So,
>basically, either SQLObject would have to pre-sort the dictionary, or it
>would have to be psychic.

Hi Chris,

Thanks for explaining that. It is not a big deal for me since I do not 
intend to use SQLObject to create the tables anyway. I have a SQL script 
that I use to do that. Since one has to specify the columns/attributes in 
the new() method anyway, the order of columns makes no difference.

Regards,

Clifford Ilkay
Dinamis Corporation
3266 Yonge Street, Suite 1419
Toronto, Ontario
Canada M4N 3P6

Tel: 416-410-3326 

Re: [SQLObject] Inserting Boolean Columns Into PostgreSQL - Again

[CLIFFORD I. <cli...@di...>]

Hello Ian,

At 13:07 09/03/2004 -0600, Ian Bicking wrote:
>Clifford Ilkay wrote:
[snip]
>>Anyway, now I can insert but, SQLObject always inserts a "t" regardless 
>>of whether I specify the boolean should be true or false. Here is the code:
>>
>>>>>from SQLObject import *
>>>>>conn = PostgresConnection('user=cilkay dbname=testdb')
>>>>>class Person(SQLObject):
>>...     _connection = conn
>>...     firstName = StringCol()
>>...     lastName = StringCol()
>>...     isMember = BoolCol()
>>...
>>
>>>>>Person.createTable()
>>>>>p = Person.new(firstName="Donald", lastName="Duck", isMember="t")
>>>>>p = Person.new(firstName="Mickey", lastName="Mouse", isMember="f")
>>>>>p = Person.new(firstName="Minnie", lastName="Mouse", isMember="0")
>>>>>p = Person.new(firstName="Pluto", lastName="Dog", isMember="False")
>>>>>p = Person.new(firstName="Goofy", lastName="Dog", isMember="false")
>
>Those are all "true" values in the Python sense (any non-empty string is 
>considered true).  0 (the integer) or None or False are all false in the 
>Python sense.

Thank you very much for pointing out this simple error on my part. Once I 
used isMember=False or isMember=True, it worked as expected.

>>testdb=# select * from person;
>>  id | last_name | is_member | first_name
>>----+-----------+-----------+------------
>>   1 | Duck      | t         | Donald
>>   2 | Mouse     | t         | Mickey
>>   3 | Mouse     | t         | Minnie
>>   4 | Dog       | t         | Pluto
>>   5 | Dog       | t         | Goofy
>>(5 rows)
>>As you can see, I tried various ways of expressing "False" but none of 
>>them seemed to work. What am I missing? Also, why is the order of the 
>>columns not the same as the order that was specified in the class definition?
>
>I'm not sure what you mean by the order.

According to the docs, the SQL create script that SQLObject would execute 
when we run Person.tableCreate() for the above class should be:

create table person (
         id int primary key autoincrement,
         first_name text,
         last_name text,
         is_member boolean
);

If you look at the output of the describe table below, you will notice that 
the order of the columns is not as we would have expected if the SQL create 
script were actually as above.

testdb=# \d person
                              Table "public.person"
    Column   |  Type   |                      Modifiers
------------+---------+------------------------------------------------------
  id         | integer | not null default nextval('public.person_id_seq'::text)
  last_name  | text    |
  is_member  | boolean |
  first_name | text    |
Indexes:
     "person_pkey" primary key, btree (id)

If the order of the columns is not as one would expect, that would wreck 
INSERT statements that rely on the position of columns rather than the 
absolute name of the columns. This is probably not a problem in SQLObject 
but it could be if one uses other tools to manipulate the same database.

Regards,

Clifford Ilkay
Dinamis Corporation
3266 Yonge Street, Suite 1419
Toronto, Ontario
Canada M4N 3P6

Tel: 416-410-3326 

[SQLObject] automatic class generation and passed in connection object

[charles b. <li...@st...>]

Hi List:

I was wondering if it is possible to use automatic class generation =
(http://sqlobject.sourceforge.net/docs/SQLObject.html#automatic-class-gen=
eration) and pass a database connection object in at the time of =
instance creation.  I was thinking something along the lines of:

from objects import Trial
u =3D Trial.new(_connection=3Dreq.conn, userName=3D"WUMPUS")
content =3D u.userName

where Trial is:
from SQLObject import *
class Trial(SQLObject):
    _fromDatabase =3D True

 When I try this I'm getting an error indicating that there is no =
connection object yet:=20

File "/<path>/SQLObject.py", line 523, in addColumnsFromDatabase
    for columnDef in cls._connection.columnsFromSchema(cls._table, cls):
AttributeError: 'NoneType' object has no attribute 'columnsFromSchema'

If I set Trial to:
from SQLObject import *
class Trial(SQLObject):
    userName =3D StringCol()

every thing seems to work ok, so I don't think its a problem with the =
connection.  It does take automatic class generation out of the picture =
though.  Maybe something to do with the order things are initialized?  I =
suppose that ultimately I should define my classes manually, so maybe =
its no big deal.

Also, I noticed that SQLObject.new() method accepts the connection as a =
keyword argument, but the standard constructor will only accept it as =
the second argument?  i.e. u =3D Trial(1, req.conn)  Is there a more =
consistent way to pass the connection to various creation methods?

Thanks in advance...

-Charles

Re: [SQLObject] Handling object cache across multiple processes

[Ian B. <ia...@co...>]

Peter Wilkinson wrote:
> Hi,
> I'm currently in the situation of needing to find an elegant way of 
> having multiple processes all use caching turned on and yet have them 
> track changes made in one of the other processes.
> 
> eg.
> Process A is running doing mainly reads, while process B is occasionally 
> making changes, process A in this situation would ideally be able to 
> deal with this and see the changed objects.
> 
> Currently I'm doing this by assuming and accepting that process B will 
> occasionally be out of sync with he reality of the database by having it 
> having it kill itself periodically. Now this works but is far from 
> elegant and ends up defeating the use of a cache which is extremely 
> handy in a process that is really only deals with the database read-only.
> 
> How have others dealt with this? Is something like putting the cache in 
> shared memory feasible?

You can expire a single object using .expire(), which will cause it to 
resync with the database when you next use the object.  You can expire 
all the objects as well, though there's no direct method for it right 
now.  Look at DBConnection.Transaction.rollback for that.

If you wanted some sort of event-based expiration, process A would have 
to be listening to process B in some way, and your objects in process B 
would have to have some notification code added.  That's a little more 
complicated, but it would keep the two processes solidly in sync.

   Ian

[SQLObject] Re: Inserting Boolean Columns Into PostgreSQL - Again

[Chris G. <ch...@il...>]

Ian answered your first question, so I'll field the second one. :)

"Clifford Ilkay" <cli...@di...> wrote in message
news:200...@di......
> testdb=# select * from person;
>  id | last_name | is_member | first_name
> ----+-----------+-----------+------------
>   1 | Duck      | t         | Donald
>   2 | Mouse     | t         | Mickey
>   3 | Mouse     | t         | Minnie
>   4 | Dog       | t         | Pluto
>   5 | Dog       | t         | Goofy
> (5 rows)
>
> As you can see, I tried various ways of expressing "False" but none of
them
> seemed to work. What am I missing? Also, why is the order of the columns
not
> the same as the order that was specified in the class definition?

I haven't looked this up, but this is probably what's happening:

When you create a subclass of an SQLObject, you're creating a new python
object. To create the table, SQLObject has to inspect this python object's
attributes to see which of them are Col() classes. Now, internally, python
stores all the attributes of a class in a dict(), so that when you look up
an attribute, it just does a lookup in the dict(). The reason they're out of
order is that dictionaries don't maintain any kind of order. The order of
the things in a dictionary depends on the order you inserted them. So,
basically, either SQLObject would have to pre-sort the dictionary, or it
would have to be psychic.

I've been doing some research into psychic computing, and the early results
have been promising, so don't rule that out! :)

[SQLObject] Handling object cache across multiple processes

[Peter W. <pw-...@te...>]

Hi,
I'm currently in the situation of needing to find an elegant way of 
having multiple processes all use caching turned on and yet have them 
track changes made in one of the other processes.

eg.
Process A is running doing mainly reads, while process B is 
occasionally making changes, process A in this situation would ideally 
be able to deal with this and see the changed objects.

Currently I'm doing this by assuming and accepting that process B will 
occasionally be out of sync with he reality of the database by having 
it having it kill itself periodically. Now this works but is far from 
elegant and ends up defeating the use of a cache which is extremely 
handy in a process that is really only deals with the database 
read-only.

How have others dealt with this? Is something like putting the cache in 
shared memory feasible?

--
peter w.

Re: [SQLObject] Inserting Boolean Columns Into PostgreSQL - Again

[Ian B. <ia...@co...>]

Clifford Ilkay wrote:
> Hi,
> 
> I had posted a message a few weeks ago about how I was having problems 
> inserting boolean columns into PostgreSQL and Ian thought it might have 
> something to do with an earlier version of Python 2.2. That was indeed the 
> case since I was using Python 2.2.2 on Mandrake 9.1. Of course that started a 
> never ending cycle upgrading various things eventually culminating in 
> installing Mandrake 10.0rc1 on another machine. Anyway, now I can insert but, 
> SQLObject always inserts a "t" regardless of whether I specify the boolean 
> should be true or false. Here is the code:
> 
> 
>>>>from SQLObject import *
>>>>conn = PostgresConnection('user=cilkay dbname=testdb')
>>>>class Person(SQLObject):
> 
> ...     _connection = conn
> ...     firstName = StringCol()
> ...     lastName = StringCol()
> ...     isMember = BoolCol()
> ...
> 
>>>>Person.createTable()
>>>>p = Person.new(firstName="Donald", lastName="Duck", isMember="t")
>>>>p = Person.new(firstName="Mickey", lastName="Mouse", isMember="f")
>>>>p = Person.new(firstName="Minnie", lastName="Mouse", isMember="0")
>>>>p = Person.new(firstName="Pluto", lastName="Dog", isMember="False")
>>>>p = Person.new(firstName="Goofy", lastName="Dog", isMember="false")

Those are all "true" values in the Python sense (any non-empty string is 
considered true).  0 (the integer) or None or False are all false in the 
Python sense.

> testdb=# select * from person;
>  id | last_name | is_member | first_name
> ----+-----------+-----------+------------
>   1 | Duck      | t         | Donald
>   2 | Mouse     | t         | Mickey
>   3 | Mouse     | t         | Minnie
>   4 | Dog       | t         | Pluto
>   5 | Dog       | t         | Goofy
> (5 rows)
> 
> As you can see, I tried various ways of expressing "False" but none of them 
> seemed to work. What am I missing? Also, why is the order of the columns not 
> the same as the order that was specified in the class definition?

I'm not sure what you mean by the order.

   Ian

[SQLObject] Inserting Boolean Columns Into PostgreSQL - Again

[Clifford I. <cli...@di...>]

Hi,

I had posted a message a few weeks ago about how I was having problems 
inserting boolean columns into PostgreSQL and Ian thought it might have 
something to do with an earlier version of Python 2.2. That was indeed the 
case since I was using Python 2.2.2 on Mandrake 9.1. Of course that started a 
never ending cycle upgrading various things eventually culminating in 
installing Mandrake 10.0rc1 on another machine. Anyway, now I can insert but, 
SQLObject always inserts a "t" regardless of whether I specify the boolean 
should be true or false. Here is the code:

>>> from SQLObject import *
>>> conn = PostgresConnection('user=cilkay dbname=testdb')
>>> class Person(SQLObject):
...     _connection = conn
...     firstName = StringCol()
...     lastName = StringCol()
...     isMember = BoolCol()
...
>>> Person.createTable()
>>> p = Person.new(firstName="Donald", lastName="Duck", isMember="t")
>>> p = Person.new(firstName="Mickey", lastName="Mouse", isMember="f")
>>> p = Person.new(firstName="Minnie", lastName="Mouse", isMember="0")
>>> p = Person.new(firstName="Pluto", lastName="Dog", isMember="False")
>>> p = Person.new(firstName="Goofy", lastName="Dog", isMember="false")

testdb=# select * from person;
 id | last_name | is_member | first_name
----+-----------+-----------+------------
  1 | Duck      | t         | Donald
  2 | Mouse     | t         | Mickey
  3 | Mouse     | t         | Minnie
  4 | Dog       | t         | Pluto
  5 | Dog       | t         | Goofy
(5 rows)

As you can see, I tried various ways of expressing "False" but none of them 
seemed to work. What am I missing? Also, why is the order of the columns not 
the same as the order that was specified in the class definition?

Regards,

Clifford Ilkay
Dinamis Corporation
3266 Yonge Street, Suite 1419
Toronto, ON  M4N 3P6
Canada

Tel: 416-410-3326

Re: [SQLObject] Regular joins?

[Ian B. <ia...@co...>]

Peter Gebauer wrote:
> Hello. I'm looking to make a regular join, but with testing.
> 
> I have two tables (simplified for the example):
> 
> class Project(SQLObject):
>   permissions = MultipleJoin("Permission")
> 
> class Permission(SQLObject):
>   person = ForeignKey("person")
>   project = ForeignKey("Project")
>   type = EnumCol(enumValues = ['A', 'B', 'C'])
> 
> The SQL for the select would be something like:
> 
> SELECT project.* FROM project, permission WHERE permission.project_id = 
> project.project_id AND permission.person_id = 666;
> 
> I don't know in the beginning of the program which projects actualy contain 
> permissions, otherwise I'd just do a myproject.permissions, what I want to 
> do is actualy select all projects that have permissions for a certain user.


Project.select(AND(Project.q.permissionsID == Permission.q.id,
                    Permission.q.personID == aPerson.id))

or

Project.select("project.project_id = permission.project_id AND 
permission.person_id = %i" % aPerson.id, clauseTables=['permission'])

Cheers.
   Ian

[SQLObject] Regular joins?

[Peter G. <pe...@fs...>]

Hello. I'm looking to make a regular join, but with testing.

I have two tables (simplified for the example):

class Project(SQLObject):
  permissions = MultipleJoin("Permission")

class Permission(SQLObject):
  person = ForeignKey("person")
  project = ForeignKey("Project")
  type = EnumCol(enumValues = ['A', 'B', 'C'])

The SQL for the select would be something like:

SELECT project.* FROM project, permission WHERE permission.project_id = 
project.project_id AND permission.person_id = 666;

I don't know in the beginning of the program which projects actualy contain 
permissions, otherwise I'd just do a myproject.permissions, what I want to 
do is actualy select all projects that have permissions for a certain user.

How can this be done?

/Peter Gebauer

Re: [SQLObject] Looking for other people's projects

[Ian B. <ia...@co...>]

Brad Bollenbach wrote:
> My talk at last year's EuroPython may be of some use to those just 
> starting out with it:
> 
>     http://www.europython.org/Talks/Slides/sqlobject_ep_talk.tar.gz

Certainly, I'll put that up (I'm waiting to make the page when I've 
collected a few more things).

> The company which I work for (until Friday, Mar 12, at which point I'm 
> making the move to independent consulting :), XSOLI, has done a credit 
> card payment processing system (that's processed about $500,000 USD 
> since last June/Julyish), and various telephony systems for a successful 
> Telco in Montreal.
> 
> Unfortunately, these systems won't demonstrate much without first paying 
> money to access them, so they may be of less use in "showing off" 
> SQLObject, but if you were interested, I could talk to Sylvain (my boss) 
> and Daniel and at least, perhaps, see if we can write up a little case 
> study about how we used it in each of these cases, and how it helped 
> make our clients happy.

Yes, a case study or even just a one-paragraph testimonial or 
description of the application would be great.

   Ian

Re: [SQLObject] Looking for other people's projects

[Brad B. <br...@bb...>]

On Monday, March 8, 2004, at 04:35  PM, Ian Bicking wrote:

> I'm revisiting the SQLObject homepage just a little for the 0.5.2 
> release, and I'd like to include links to any applications using 
> SQLObject, examples, wrappers, documents, articles, etc.  So if you 
> have or know of something, please email me.
>
> If you have some code on your disk that you're not sure how to 
> distribute, email me too and maybe we can find a place for it in the 
> repository somewhere (ala webware-sandbox.sf.net).

My talk at last year's EuroPython may be of some use to those just 
starting out with it:

     http://www.europython.org/Talks/Slides/sqlobject_ep_talk.tar.gz

The company which I work for (until Friday, Mar 12, at which point I'm 
making the move to independent consulting :), XSOLI, has done a credit 
card payment processing system (that's processed about $500,000 USD 
since last June/Julyish), and various telephony systems for a 
successful Telco in Montreal.

Unfortunately, these systems won't demonstrate much without first 
paying money to access them, so they may be of less use in "showing 
off" SQLObject, but if you were interested, I could talk to Sylvain (my 
boss) and Daniel and at least, perhaps, see if we can write up a little 
case study about how we used it in each of these cases, and how it 
helped make our clients happy.

--
Brad Bollenbach

[SQLObject] ANN: SQLObject 0.5.2

[Ian B. <ia...@co...>]

SQLObject 0.5.2 released
------------------------

Homepage:
   http://sqlobject.org
Download:
    
http://prdownloads.sourceforge.net/sqlobject/SQLObject-0.5.2.tar.gz? 
download
News:
   http://sqlobject.org/docs/News.html#sqlobject-0-5-2

What's Changed?
---------------

0.5.2 is a bug fix release, particularly a thread-related bug when  
using extended selects.  All users are recommended to upgrade.

What is it?
-----------

SQLObject is an object relational mapper.  It allows you to easily  
create an object interface to your database -- tables are classes, rows  
are instances.  Its goals are ease of use and low barrier to entry,  
while maintaining the ability to customize and extend your classes as  
your needs grow.

--
Ian Bicking | ia...@co... | http://blog.ianbicking.org