Re: [SQLObject] sqlobject-discuss Digest, Vol 61, Issue 1
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
Menu
▾
▴
Re: [SQLObject] sqlobject-discuss Digest, Vol 61, Issue 1
|
From: Peter D. <pet...@gm...> - 2011-06-13 19:45:51
|
Oleg,
Thanks for the reply. The actual error is
OperationalError("Can't create table 'conxt.#sql-d58_57' (errno: 150)",)
The database name is conxt.
If I ignore this error everything runs fine. You are right that 'organizer'
has not been created yet. Is it OK to ignore this?
----- Original Message -----
From: <sql...@li...>
To: <sql...@li...>
Sent: Monday, June 13, 2011 1:55 PM
Subject: sqlobject-discuss Digest, Vol 61, Issue 1
> Send sqlobject-discuss mailing list submissions to
> sql...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
> or, via email, send a message with subject or body 'help' to
> sql...@li...
>
> You can reach the person managing the list at
> sql...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of sqlobject-discuss digest..."
>
>
> Today's Topics:
>
> 1. Re: SQLObject 1.0.0 problem with Py 2.4 (Christoph Zwerschke)
> 2. Re: SQLObject 1.0.0 problem with Py 2.4 (Petr Jake?)
> 3. SQLObject 1.0.1 (Oleg Broytman)
> 4. Re: SQLObject 1.0.1 (Christoph Zwerschke)
> 5. SQLObject and Multiprocessing (Gert Burger)
> 6. Re: SQLObject and Multiprocessing (Oleg Broytman)
> 7. Fw: Creating Tables (Peter Douma)
> 8. Re: Creating tables (Oleg Broytman)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 26 May 2011 22:16:57 +0200
> From: Christoph Zwerschke <ci...@on...>
> Subject: Re: [SQLObject] SQLObject 1.0.0 problem with Py 2.4
> To: sql...@li...
> Message-ID: <4DD...@on...>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Am 26.05.2011 21:47 schrieb Oleg Broytman:
> > There is no need for opinions - I'm going to restore Python 2.4
> > compatibility and release SQLObject 1.0.1, just not immediately
>
> Ok, thanks. If you need any help with testing, let me know.
>
> -- Christoph
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 26 May 2011 22:32:46 +0200
> From: Petr Jake? <pet...@tp...>
> Subject: Re: [SQLObject] SQLObject 1.0.0 problem with Py 2.4
> To: sql...@li...
> Message-ID: <BAN...@ma...>
> Content-Type: text/plain; charset="utf-8"
>
> Quis custodiet ipsos custodes? Who does fix bugs in test? ;-)
>
> Nice, thanks :D
>
> Petr
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 3
> Date: Mon, 30 May 2011 15:19:14 +0400
> From: Oleg Broytman <ph...@ph...>
> Subject: [SQLObject] SQLObject 1.0.1
> To: SQLObject discussion <sql...@li...>
> Message-ID: <201...@is...>
> Content-Type: text/plain; charset=us-ascii
>
> Hello!
>
> I'm pleased to announce version 1.0.1, a bugfix 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.1
>
> News and changes:
> http://sqlobject.org/News.html
>
>
> What's New
> ==========
>
> * A syntax incompatibility was fixed in SQLiteConnection that prevented
> SQLObject to be used with Python 2.4.
>
> 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.
>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 30 May 2011 18:40:59 +0200
> From: Christoph Zwerschke <ci...@on...>
> Subject: Re: [SQLObject] SQLObject 1.0.1
> To: sql...@li...
> Message-ID: <4DE...@on...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Am 30.05.2011 13:19, schrieb Oleg Broytman:
>> I'm pleased to announce version 1.0.1, a bugfix release of branch 1.0
>> of SQLObject.
>
> Thanks! It's now working again with Py 2.4.
>
> -- Christoph
>
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 01 Jun 2011 10:39:42 +0200
> From: Gert Burger <ger...@gm...>
> Subject: [SQLObject] SQLObject and Multiprocessing
> To: SQLObject discussion <sql...@li...>
> Message-ID: <4DE...@gm...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi
>
> Can one use SQLObject with multiprocessing? For example can one create
> extra processes using the multiprocessing.Process using the 'inherited'
> sqlobject environment to handle certain database queries?
>
> Regards
> Gert Burger
>
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 1 Jun 2011 13:01:54 +0400
> From: Oleg Broytman <ph...@ph...>
> Subject: Re: [SQLObject] SQLObject and Multiprocessing
> To: sql...@li...
> Message-ID: <201...@is...>
> Content-Type: text/plain; charset=us-ascii
>
> On Wed, Jun 01, 2011 at 10:39:42AM +0200, Gert Burger wrote:
>> Can one use SQLObject with multiprocessing? For example can one create
>> extra processes using the multiprocessing.Process using the 'inherited'
>> sqlobject environment to handle certain database queries?
>
> I doubt it's possible to share an open connection between processes.
> In a different process you are to open a different connection and that
> would lead to problems with transactions. Perhaps its possible to open a
> different connection and run transaction-less queries.
>
> Oleg.
> --
> Oleg Broytman http://phdru.name/ ph...@ph...
> Programmers don't die, they just GOSUB without RETURN.
>
>
>
> ------------------------------
>
> Message: 7
> Date: Mon, 13 Jun 2011 13:48:08 -0400
> From: "Peter Douma" <pet...@gm...>
> Subject: [SQLObject] Fw: Creating Tables
> To: <sql...@li...>
> Message-ID: <34A6E1E07669401CA91538CFBCFCC49B@LapTop>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> I just started using SQLObject and I would like to use it with Flask. So I
> figured I would separate the models from the actual database working,
> similar to what Django does.
>
> I create the following function to open up the models files and create the
> tables:
>
> import inspect
> import models
>
> def __init__(self):
> members = inspect.getmembers(models, inspect.isclass)
> for name, cls in members:
> if cls.__module__ == 'models':
> try:
> cls.createTable(ifNotExists=True)
> except OperationalError, e:
> raise OperationalError(e)
>
>
> When I get to this model
>
> class Event(SQLObject):
> event_id = IntCol( unique = True )
> describ = StringCol()
> date = DateTimeCol(default = DateTimeCol.now)
> organizer = ForeignKey("Organizer", default=None)
> sponsers = MultipleJoin("Sponser")
> attendees = RelatedJoin("Attendee")
>
> I get the following error:
> conxt.#sql-d58_2b' (errno: 150)
>
> If I run it again, everything works fine. The first time through the table
> is created, but not the the related tables.
>
>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 8
> Date: Mon, 13 Jun 2011 21:55:06 +0400
> From: Oleg Broytman <ph...@ph...>
> Subject: Re: [SQLObject] Creating tables
> To: sql...@li...
> Message-ID: <201...@is...>
> Content-Type: text/plain; charset=us-ascii
>
> On Mon, Jun 13, 2011 at 01:48:08PM -0400, Peter Douma wrote:
>> I just started using SQLObject
>
> Welcome!
>
>> When I get to this model
>>
>> class Event(SQLObject):
>> event_id = IntCol( unique = True )
>> describ = StringCol()
>> date = DateTimeCol(default = DateTimeCol.now)
>> organizer = ForeignKey("Organizer", default=None)
>> sponsers = MultipleJoin("Sponser")
>> attendees = RelatedJoin("Attendee")
>>
>> I get the following error:
>> conxt.#sql-d58_2b' (errno: 150)
>
> The error doesn't look like it it's from SQLObject. Can you provide
> more details? Database? driver? full traceback?
>
>> If I run it again, everything works fine. The first time through the
>> table is created, but not the the related tables.
>
> Could it be a problem with ForeignKey pointed to a table
> ('organizer') that hasn't been created yet?
>
> Oleg.
> --
> Oleg Broytman http://phdru.name/ ph...@ph...
> Programmers don't die, they just GOSUB without RETURN.
>
>
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
>
> ------------------------------
>
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>
>
> End of sqlobject-discuss Digest, Vol 61, Issue 1
> ************************************************
>
|
