openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Holloway (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-626) @JoinColumn with name attribute causes exception on 1.2.0.
Date Tue, 17 Jun 2008 18:23:45 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605685#action_12605685
] 

Tim Holloway commented on OPENJPA-626:
--------------------------------------

Thanks, Fay.

Don't be surprised if you encounter more of these funny columnDefinition's. As far as I can
determine, there seems to have been a bug(?) in the earlier OpenJPA releases where columnDefinition
was being interpreted as though it was the name= attribute. That stopped working somewhere
around release 1.0. I don't know how I ended up using them, but I thought I'd flushed them
all out. Obviously not.

Here's the context I'm failing on:

       @Transactional
 	public Trips loadTripStops(Trips editTrip) {
		final Trips trip = entityManager.merge(editTrip);
		@SuppressWarnings("unused")
		List<TripStops> childList = trip.getTripStops();
		return trip;
	}

And here's the latest SQL, after making the repair:

<openjpa-1.2.0-SNAPSHOT-r422266:661817M nonfatal general error> org.apache.openjpa.persistence.PersistenceException:
ERROR: column t0.busstops_stop_id does not exist {prepstmnt 27436928 SELECT t0.trip_stop_id,
t0.active_stop, t0.arrive_time, 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.depart_time, t0.end_of_line,
t0.inbound, t0.ROUTES_ROUTE_ID FROM public.trip_stops t0 LEFT OUTER JOIN public.bus_stops
t1 ON t0.BUSSTOPS_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.TRIPS_TRIP_ID
= ? ORDER BY t0.arrive_time ASC [params=(int) 11]} [code=0, state=42703]


> @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-src-1.zip, 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.


Mime
View raw message