Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 72263 invoked from network); 5 Jun 2008 22:57:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Jun 2008 22:57:09 -0000 Received: (qmail 74873 invoked by uid 500); 5 Jun 2008 22:57:11 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 74855 invoked by uid 500); 5 Jun 2008 22:57:11 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 74844 invoked by uid 99); 5 Jun 2008 22:57:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2008 15:57:11 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2008 22:56:23 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id F20F1234C12E for ; Thu, 5 Jun 2008 15:56:44 -0700 (PDT) Message-ID: <1771240390.1212706604979.JavaMail.jira@brutus> Date: Thu, 5 Jun 2008 15:56:44 -0700 (PDT) From: "Tim Holloway (JIRA)" To: dev@openjpa.apache.org Subject: [jira] Commented: (OPENJPA-626) @JoinColumn with name attribute causes exception on 1.2.0. In-Reply-To: <1527724416.1212688545356.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/OPENJPA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602829#action_12602829 ] Tim Holloway commented on OPENJPA-626: -------------------------------------- Long story short - looks like it should be working. I did note some irregularities on the AnnotationPersistenceMappingParser, but they're for other tables and might be undiscovered bad annotations rather than bugs. > @JoinColumn with name attribute causes exception on 1.2.0. > ----------------------------------------------------------- > > Key: OPENJPA-626 > URL: https://issues.apache.org/jira/browse/OPENJPA-626 > Project: OpenJPA > Issue Type: Bug > Affects Versions: 1.2.0 > Reporter: Michael Dick > Attachments: OPENJPA-626-vars-1.txt > > > Creating Issue on behalf of Tim Holloway. Here's his email to the dev mailing list : > @ManyToOne(fetch=FetchType.EAGER, cascade=CascadeType.MERGE) > @JoinColumn(name="bus_stop_id") > private BusStops busStop; > Works in release 1.0.2: > SELECT t0.schedule_stop_id, t1.stop_id, t1.description, t1.elevation, > t1.in_ > service_date, t1.inbound, t1.latitude, t1.longitude, > t1.out_service_date, t1.sheltered, t1.street1_block, > t2.street_direction_id, t2.description, t1.street1_name, t1.street1 > _qualifier, t3.street_type_id, t3.description, t1.street2_block, > t4.street_direction_id, t4.description, t1.street2_name, > t1.street2_qualifier, t5.street_type_id, t5.descrip > tion, t1.waypoint, t0.clock_point, t0.comments, t0.in_service, > t0.in_service_date, t0.inbound, t0.out_service_date, t0.outbound, > t0.schedule_id, t0.stop_sequence, t0.terminu > s, t0.transfer_point FROM public.schedule_stops t0 LEFT OUTER JOIN > public.bus_stops t1 ON t0.bus_stop_id = t1.stop_id LEFT OUTER JOIN > public.lk_street_directions t2 ON t1.st > reet1_direction = t2.street_direction_id LEFT OUTER JOIN > public.lk_street_types t3 ON t1.street1_type = t3.street_type_id LEFT > OUTER JOIN public.lk_street_directions t4 ON t > 1.street2_direction = t4.street_direction_id LEFT OUTER JOIN > public.lk_street_types t5 ON t1.street2_type = t5.street_type_id WHERE > t0.schedule_id = ? ORDER BY t0.stop_seque > nce ASC [params=(int) 50] > Uses synthesized column name instead of declared name in today's CVS > snapshot: > ERROR: column t0.busstop_stop_id does not exist {prepstmnt 17939164 > SELECT t0.schedule_stop_id, t1.stop_id, t1.description, t1.elevation, > t1.in_service_date, t1.inbound, t1.latitude, t1.longitude, > t1.out_service_date, t1.sheltered, t1.street1_block, > t2.street_direction_id, t2.description, t1.street1_name, > t1.street1_qualifier, t3.street_type_id, t3.description, > t1.street2_block, t4.street_direction_id, t4.description, > t1.street2_name, t1.street2_qualifier, t5.street_type_id, > t5.description, t1.waypoint, t0.clock_point, t0.comments, t0.in_service, > t0.in_service_date, t0.inbound, t0.out_service_date, t0.outbound, > t0.SCHEDULE_SCHEDULE_ID, t0.stop_sequence, t0.terminus, > t0.transfer_point > FROM public.schedule_stops t0 > LEFT OUTER JOIN public.bus_stops t1 > ON t0.BUSSTOP_STOP_ID = t1.stop_id > LEFT OUTER JOIN public.lk_street_directions t2 > ON t1.street1_direction = t2.street_direction_id > LEFT OUTER JOIN public.lk_street_types t3 ON t1.street1_type = > t3.street_type_id LEFT OUTER JOIN public.lk_street_directions t4 ON > t1.street2_direction = t4.street_direction_id LEFT OUTER JOIN > public.lk_street_types t5 ON t1.street2_type = t5.street_type_id WHERE > t0.SCHEDULE_SCHEDULE_ID = ? ORDER BY t0.stop_sequence ASC [params=(int) > 50]} [code=0, state=42703] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.