Rick, Thank you for considering my suggestion. Putting it in JDBCFetchConfiguration is pretty much boilerplate. 1. Declare a boolean ignoreFKinDFG or something in JDBCFetchConfigurationImpl$JDBCConfigurationState 2. Copy the field value in copy(FetchConfiguration fc) 3. If you want this boolean be also supported via query hints, then follow similar pattern used in other variables 4. Facade the accessor/mutator in JDBCFetchPlan
If an option is not JDBC-specific, then the same tactics applies to FetchConfigurationImpl$ConfigurationState If you are wondering why ConfigurationState is separate from FetchConfiguration, the answer is to guard against concurrent usage. ----- Pinaki Poddar Chair, Apache OpenJPA Project -- View this message in context: http://openjpa.208410.n2.nabble.com/jira-Created-OPENJPA-2039-FKs-for-EAGER-fields-that-are-not-in-the-current-fetchplan-aren-t-selected-tp6674335p6689014.html Sent from the OpenJPA Developers mailing list archive at Nabble.com.
