AW: Can't handle same column name twice - possibly a bug in village?

2004-12-16 Thread Thomas Fischer
Hi Daniel, looking into village, it extracts the tablename from the metadata and looks if there are different tables (com.workingdogs.village.Column.populate()) Now, my oracle driver returns null as tablename, so village assumes the results stem from a single table, the crucial call being

AW: Can't handle same column name twice - possibly a bug in village?

2004-12-16 Thread Vitzethum, Daniel
Hello Henning and Thomas, > I still cannot reproduce your error *sigh* > I used your code below and get > [{'1','10','100','100','20'}] Now that's really strange to me. Both of you tell me that village is not responsible for that, but the error occurs - in my environment - definitely _below_ Tor

Re: AW: Can't handle same column name twice - possibly a bug in village?

2004-12-15 Thread Henning P. Schmiedehausen
Thomas Fischer <[EMAIL PROTECTED]> writes: Can you add this test to the CVS? Regards Henning >Hi Daniel, >I cannot reproduce this error, see appended test case against the tutorial >database schema. I suppose you use your JoinHelper. Are you sure it is not >a bug in ther

AW: Can't handle same column name twice - possibly a bug in village?

2004-12-15 Thread Thomas Fischer
Daniel, I still cannot reproduce your error select * from TEST_LENDING; select * from TEST_GROUP; select * from TEST_PERSON; L_ID G_ID -- -- 100 20 G_ID -- 10 20 P_ID G_ID L_ID --

Re: AW: Can't handle same column name twice - possibly a bug in village?

2004-12-15 Thread Henning P. Schmiedehausen
"Vitzethum, Daniel" <[EMAIL PROTECTED]> writes: >builds a correct Criteria with qualified columns that works >well on DB: > SELECT > TEST_PERSON.P_ID, TEST_PERSON.G_ID, TEST_PERSON.L_ID > , TEST_LENDING.L_ID, TEST_LENDING.G_ID > FROM > TEST_PERSON > , TEST_LENDING > WHERE > TEST_PERSON.L_I

AW: Can't handle same column name twice - possibly a bug in village?

2004-12-15 Thread Vitzethum, Daniel
Hi Richard, Hi Thomas, Thomas: > I suppose you use your JoinHelper. you are right, as usual ;-) > Are you sure it is not a bug in there ? I am, as I had tested the same situation with just two tables joined with a Torque-generated "doSelectJoin..." method. The problem is a bit different, I will

AW: Can't handle same column name twice - possibly a bug in village?

2004-12-15 Thread Thomas Fischer
Hi Daniel, I cannot reproduce this error, see appended test case against the tutorial database schema. I suppose you use your JoinHelper. Are you sure it is not a bug in there ? "Vitzethum, Daniel" <[EMAIL PROTECTED]> schrieb am 14.12.2004 17:21:38: > Hi Thomas, > > >> In addition, where is

Re: AW: Can't handle same column name twice - possibly a bug in village?

2004-12-14 Thread Richard Bayet
Vitzethum, Daniel wrote: Hi Thomas, In addition, where is the home of the village project? http://wiki.apache.org/db-torque/FrequentlyAskedQuestions I admit, it was the obvious again. A workaround for my problem certainly is to have unique column names in the whole data model, what means some wor

AW: Can't handle same column name twice - possibly a bug in village?

2004-12-14 Thread Vitzethum, Daniel
Hi Thomas, >> In addition, where is the home of the village project? > http://wiki.apache.org/db-torque/FrequentlyAskedQuestions I admit, it was the obvious again. A workaround for my problem certainly is to have unique column names in the whole data model, what means some work for us. Indeed it