[sqlalchemy] Re: Problem:maximum recursion depth exceeded - Ticket #1081

2009-08-25 Thread Marin
I run the tests and there were several errors. One of them is test.orm.test_unitofwork.ForeignPKTest.test_basic I can't find the a way of running it in PyDev to see what went wrong. Any help on how to run this single test in debug mode under PyDev? -- Marin

[sqlalchemy] Problem:maximum recursion depth exceeded - Ticket #1081

2009-08-18 Thread Marin
I reported the bug a year ago. It seems nobody is interested in fixing it. So, this is my first try, but i don't know how to use the regression test to see if it is correct. Can anybody help me? unitofwork.py: class UOWExecutor(object): Encapsulates the execution traversal of a

[sqlalchemy] Re: foreign_keys question

2008-10-27 Thread Marin
Thanks. I tracked the problem in the SQL script I was using to create the new tables. The new script accidentally deleted the previous foreign key. It is fixed now and it works correctly. --~--~-~--~~~---~--~~ You received this message because you are subscribed to

[sqlalchemy] foreign_keys question

2008-10-21 Thread Marin
I am using SA to map existing tables from my database. I have mapped the whole database without using any foreign_key argument for the mapper properties. After adding 3 new tables with corresponding foreign keys, SA is forcing me to add the foreign_key argument for the new mappings. Is there a

[sqlalchemy] in_ SADeprecationWarning

2008-07-03 Thread Marin
I use the following code: query = meta.Session.query(db.Object) all_objects = [1,2,3] objects = query.filter(db.Object.ObjectID.in_(*all_objects)).all() And I get this error: SADeprecationWarning: passing in_ arguments as varargs is deprecated, in_ takes a single argument that is a sequence or a

[sqlalchemy] Re: in_ SADeprecationWarning

2008-07-03 Thread Marin
I got it... I wanted to replicate the error in a single file, but I couldn't have them booth. I realized then that the problem was in 2 different SA version installed on my computer. Now that i removed the older everything works correctly. On Jul 3, 1:48 pm, [EMAIL PROTECTED] wrote: SA version?

[sqlalchemy] Re: Problem:maximum recursion depth exceeded

2008-06-23 Thread Marin
I was trying to do something yesterday evening and I found something strange. After running this code: q = Q() for j in range(1): a = A() a.Q = q a.C = WC() I get this graph edges (tuples): import pprint ppp = pprint.PrettyPrinter(indent=4) ppp.pprint([(x.class_,

[sqlalchemy] Re: Problem:maximum recursion depth exceeded

2008-06-22 Thread Marin
Thx for the info. I took a short look at the code yesterday, and I can't understand why do you use the _organize_as_tree function. The ordered list of nodes that the topological sort returned should be enough for the flush. Maybe I am missing the idea behind the code (but that is OK since this is

[sqlalchemy] Re: Problem:maximum recursion depth exceeded

2008-06-22 Thread Marin
It sounds like a typical case of YAGNI. But, if the code works with the tree structure, could it be fix by just supplying the sorted list instead of the tree? As a list could be seen as a flat tree, the algorithm should work if the organize_as_tree does nothing.

[sqlalchemy] Re: Problem:maximum recursion depth exceeded

2008-06-22 Thread Marin
Heh, same here. The weekend is over and I have to go back to other stuff. I'll try to do something if could find the time. yes, that was the idea. Didn't work for some reason, but I didn't try that hard. --~--~-~--~~~---~--~~ You received this message because

[sqlalchemy] Re: Problem:maximum recursion depth exceeded

2008-06-21 Thread Marin
I know that is complicated, but I'll still take a look at it. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from

[sqlalchemy] Re: Problem:maximum recursion depth exceeded

2008-06-20 Thread Marin
Should I report this as a ticket on the SA trac site? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group,

[sqlalchemy] Re: Problem:maximum recursion depth exceeded

2008-06-20 Thread Marin
I see that someone just copy/paste that code I wrote in the ticket 1081. I'll try to take a look and fix it myself this weekend if I could spare the time. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy

[sqlalchemy] Problem:maximum recursion depth exceeded

2008-06-18 Thread Marin
I get this error when i try to execute the folowing code (Test, Section, Question, Answer are mepped tables): test = Test() section = Section() section.Test=test for i in range(60): q=Question() q.Section=section for j in range(6) a = Answer() a.Question = q

[sqlalchemy] Re: Problem:maximum recursion depth exceeded

2008-06-18 Thread Marin
cant really tell unless you provide a fully functional, as simple as possible test case, preferably against sqlite, which can be run with no dependencies. I'll try to make one. I tried to fix it doday and got that the next code does not produce the error: test = Test() section = Section()

[sqlalchemy] Inheritacne, reflecting tables and CircularDependencyError

2008-06-04 Thread Marin
I have a PostgreSQL database with 3 tables: Object, Role and User: CREATE TABLE Object ( ObjectID BIGINT NOT NULL DEFAULT NEXTVAL('SEQ_ObjectID'), ObjectTypeID INT NOT NULL, OwnerUserID BIGINT NOT NULL, CreatedTimestamp TIMESTAMP WITH TIME ZONE NOT NULL DEFAULT NOW(),