Hi Nicolas, thanks looking better.
Could you now change it for longer runs? If I think of 2K invocations,
each taking 5ms, that's not more than 10 seconds.. It took me several
minutes to load all the data needed for the test, then just some
seconds to run the tests.. not worth the load time ;)
To c
>
> On a side note, what do you need System.exit(0); for ? You should
> close the SessionFactory.
>
Because i m better with geo/data than with code =)
Thanks for pointing me the right direction.
The last numbers series is from a 50k calls run in radian mode that lasted
45 minutes.
For each center
Hi,
Just to be sure, there is currently any test on the suite about composite
id right ?
As I said on github, I'm taking this one and then OGM-179 (duplication
between "id" and "_id") which concerns also the ID field management.
Do you have any suggestions, metaphysical thoughts, or anything els
No test yet, or they would have failed :)
I did write an email on the subject a while ago ont he subject of (composite)
id in mongodb, you will have to dig it up.
On 15 mai 2012, at 18:08, Guillaume SCHEIBEL wrote:
> Hi,
>
> Just to be sure, there is currently any test on the suite about compo
My current thinking here is that the discrimination would only be
definable at the root of a mapped inheritance hierarchy.
Thoughts? Votes?
--
st...@hibernate.org
http://hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
http
Multi-tenant setups sometimes have data that is shared between the
tenants (codec tables, etc).
I think the first question is do we want to support this mixing? I
think it is common enough that it is worthwhile to support it. And I do
not think it is complicated enough to be painful to implem
Definitely seems reasonable for now, especially considering this will be our
first implementation. I guess I'm also assuming we have no user requests that
would oppose this decision.
On May 15, 2012, at 11:45 AM, Steve Ebersole wrote:
> My current thinking here is that the discrimination would
I'd agree. It would seem strange to assume the lack of inheritance in this
case and have to annotate multi-tenancy throughout the chain of associations.
On May 15, 2012, at 12:04 PM, Steve Ebersole wrote:
> Multi-tenant setups sometimes have data that is shared between the
> tenants (codec tab
On 15 May 2012 17:08, Guillaume SCHEIBEL wrote:
> Hi,
>
> Just to be sure, there is currently any test on the suite about composite
> id right ?
> As I said on github, I'm taking this one and then OGM-179 (duplication
> between "id" and "_id") which concerns also the ID field management.
>
> Do y
Hi Steve,
> Take 'temporaryIdTableDDL' as the perfect example. Hibernate cannot know at
> start up (building the SessionFactory) that the application will or will not
> use HQL updates/deletes against "multi-table structures" that would therefore
> need access to 'temporaryIdTableDDL'?
>
> An
Hi Sanne,
> Andrej, what's the overall size you would save by dropping the
> Configuration object?
16187776 bytes.
Best regards,
Andrej Golovnin
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hiber
Hi all,
finally I have found the cause of this problem.
But before I describe what caused it, I would like to make two suggestions:
1. Consider avoiding usage of String#toLowerCase() and String#toUpperCase()
without specifying a Locale. Users running Hibernate on systems with
Turkish as def
12 matches
Mail list logo
