The good news is that I am following you :D
I think one of the option is some API to which you can pass the (JPA)
Type, a Path from root and it would return a structure qualifying the
embedded info and not just the embeddable.
I'm making things up here
//might not even need the type, could be gu
The contextualization would only work when user calls metamodel.entity(). Not
the other methods
> On 22 juil. 2016, at 11:14, Emmanuel Bernard wrote:
>
> The good news is that I am following you :D
>
> I think one of the option is some API to which you can pass the (JPA)
> Type, a Path from ro
While this topic is hot and the type handlers will not be
backwards-compatible, I think they should have some access to the
connection-specific Dialect. I have started (but largely paused) an
implementation of Array datatypes, but it's highly dependent on instance
type-checking of WrapperOptions ug
Vlad and I already spoke about some form of native (or at least more easily
user defined) support for SQL ARRAY types. However, I do not know that
that will extend to ARRAYs of entities.
That said... all the methods to read a value on Type will be passed a
Session. I think that was a mistake in
I get what you mean. We have to start from a "bindable" root. FWIW other
types beside entity could be a "contextualization root" depending on the
Metamodel method signature.
Obviously the return from Metamodel#embeddable(Class) could not. But, we
could expose methods that would allow access the
Some preliminary thoughts are inline. Like I said in the earlier reply I
am still trying to distill this in total.
On Fri, Jul 22, 2016 at 4:14 AM Emmanuel Bernard
wrote:
> The good news is that I am following you :D
>
> I think one of the option is some API to which you can pass the (JPA)
> Ty
I've updated the microdata on our blog.
I used the google validation page to check the result:
https://search.google.com/structured-data/testing-tool/u/0/?hl=EN#url=http%3A%2F%2Fin.relation.to%2F
I'm not familiar with microdata, if you think that something is wrong
let me know.
I have a question
Hibernate is fine.
On Fri 2016-07-22 16:57, Davide D'Alto wrote:
> I've updated the microdata on our blog.
> I used the google validation page to check the result:
> https://search.google.com/structured-data/testing-tool/u/0/?hl=EN#url=http%3A%2F%2Fin.relation.to%2F
>
> I'm not familiar with mic
I am eager to see what you think of my third option in my email. I dread
there is a technical blocker somewhere but it would be quite a nice
solution if that's not the case.
On Fri 2016-07-22 14:59, Steve Ebersole wrote:
> Some preliminary thoughts are inline. Like I said in the earlier reply I
>
Still letting it percolate :)
On Fri, Jul 22, 2016 at 11:35 AM Emmanuel Bernard
wrote:
> I am eager to see what you think of my third option in my email. I dread
> there is a technical blocker somewhere but it would be quite a nice
> solution if that's not the case.
>
> On Fri 2016-07-22 14:59,
It looks like it will be next week (hopefull). We have a critical issue to
fix. Once that's done, I'll do the release.
On Wed, Jul 20, 2016 at 8:05 AM, Chris Cranford wrote:
> Sanne -
>
> I'm under the impression that Gail has plans to do a 5.0.10 / 5.1.1 late
> this week if all goes according t
+1
On Mon, Jul 18, 2016 at 6:25 AM, Steve Ebersole wrote:
> This is the comment that will now be added to an issue whenever an issue is
> transitioned to "Awaiting Test Case":
>
> Please attach a short but complete [test case|
> https://github.com/hibernate/hibernate-orm/wiki/Test-Case-Guide] th
On Fri, Jul 22, 2016 at 4:14 AM Emmanuel Bernard
wrote:
An alternative that I can think of is as follows. I'm assuming that the
> data that needs to be contextualized by the path is mapping in nature or
> at least not at all represented in the JPA types.
> Each (JPA) type instance would be inhere
Hi all,
So after having discussed this issue with Emmanuel:
1/ is correct. It's the behavior we expect considering the ORM behavior. If we
want the postal_code to be nested in homeAddress, we need to use @Column(name =
"homeAddress.postal_code") or @AttributeOverride(name="zipCode",
column=@Co
14 matches
Mail list logo
