You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure I understand the reason why the Oracle script is named oracle10g rather than oracle but this leads to some duplicated logic where we have to guess the platform based on the databaseProductName returned by the datasource meta-data.
If we could have oracle as in Spring Session, that would allows us to remove that unnecessary logic.
Affects: 3.0.7
The text was updated successfully, but these errors were encountered:
It's been like that in Spring Batch since the beginning (i.e. 2007), when 10g was actually new. I don't know if it's a great idea to change it now. Maybe we could add a copy with a different name?
I know it's been like that for a long time. My point is that it's not really relevant anymore. And the duplication logic outside of batch is pretty bad.
Stéphane Nicoll opened BATCH-2545 and commented
I am not sure I understand the reason why the Oracle script is named
oracle10g
rather thanoracle
but this leads to some duplicated logic where we have to guess the platform based on thedatabaseProductName
returned by the datasource meta-data.If we could have
oracle
as in Spring Session, that would allows us to remove that unnecessary logic.Affects: 3.0.7
The text was updated successfully, but these errors were encountered: