Like I said in the original email, the connection may or may not be
available. Which means we cannot rely on it being available. Nor do
we rely on it being available today either btw. The difference is just
that today in those cases we expect the user to manually name the
dialect to use.
On
hmm - any reason why jpa won't pass in DatabaseMetadata ?
how would one identify name and version anyway if that is not available ?
/max
On 29 Aug 2012, at 16:43, Steve Ebersole wrote:
> I think we need to consider changing DialectResolver to fit with some
> upcoming JPA 2.1 features.
>
> JP
I think we need to consider changing DialectResolver to fit with some
upcoming JPA 2.1 features.
JPA 2.1 is adding some form of schema export. The initial plan there is
to identify the "dialect" to target by passing in the (1) database name
and (2) database version as it would come from JDBC D
On 28 Jan 2012, at 9:49 PM, Steve Ebersole wrote:
> Following a discussion about this on the dev IRC I did a little bit of
> this work today.
>
> See:
> 1)
> http://transcripts.jboss.org/channel/irc.freenode.org/%23hibernate-dev/2012/%23hibernate-dev.2012-08-28.log.html
> 2) https://hibernate.
> Steve, I'll take a look at StrategySelector in the morning. Martin, if
> you're interested, I'm willing to help prototype it with you.
@Brett
Help and information is always welcome - I will contact you directly to
clarify, how we could best work together.
> I am not familiar enough to know how
