Hi,
I was discussing with Steve on the HipChat page yesterday that we should
probably enable these forum options:
Enable queued posts:
Ability to put registered users posts to post approval if their post count
is lower than the specified value below. This setting has no effect on the
permission se
I meant something like:
session.persistAll(List entities);
Because all entities are passed in a single method call, the persistence
context can start managing those and also try to use batching if the
configuration suggests using JDBC batching.
That could be much easier than delaying the IDENTIT
Thanks for investigating it.
On Mon, Dec 7, 2015 at 9:40 PM, Gail Badner wrote:
> This is something that got broken in 4.3 when we moved to using load
> plans. I agree this needs to be fixed. I will get to this later this week.
>
> On Mon, Dec 7, 2015 at 12:18 AM, Vlad Mihalcea
> wrote:
>
>> Hi
This is something that got broken in 4.3 when we moved to using load plans.
I agree this needs to be fixed. I will get to this later this week.
On Mon, Dec 7, 2015 at 12:18 AM, Vlad Mihalcea
wrote:
> Hi,
>
> Someone on Twitter pointed out this issue:
> https://hibernate.atlassian.net/browse/HHH-
MySQL is the first choice for many projects (even if PostgreSQL is more
advanced) and the AUTO_INCREMENT is the only choice a DBA will approve.
The TABLE identifier generator is too heavyweight and any external DB user
will have to know how it works for inserting new rows.
I'll run some tests for
WDYM by "Hibernate-native Batching API"?
On Mon, Dec 7, 2015 at 12:57 PM Vlad Mihalcea
wrote:
> I'm sure it require a significant change since the persistence context is
> very much tied to the entity identifier.
> Theoretically, it could work because the identifier is required for
> database o
I'm sure it require a significant change since the persistence context is
very much tied to the entity identifier.
Theoretically, it could work because the identifier is required for
database operations and for merging as well.
Because the EntityIdentityInsertAction already has the isDelayed prope
On Sat, Dec 5, 2015 at 11:46 PM Vlad Mihalcea
wrote:
> HI,
>
> I always wandered why the identity generator needs to assign an identifier
> prior to flushing.
>
In general, how else do you propose to obtain the identifier with which we
can associate the entity into the PersistenceContext? That
Not so much an alternative criteria API, more an alternative representation
of (what will become) the internal Hibernate understanding semantically of
a query. I do see the benefit in that, which is why I proposed it and
designed this all with that ultimately in mind :). Honestly, I am at the
poi
As soon as a new entity becomes "managed", it needs to be tracked by
the Persistence Context (the container within each Session)..
obviously, as otherwise we wouldn't be able to know what needs to be
eventually flushed.
And within the PC each entity must have an id assigned: it would be
nice to ha
Thanks Sanne,
I have no idea how Aksimet works but I noticed it does a good good on
WordPress.
It could work as a service and that might make the integration more
difficult.
One other option would be to make all post require manual validation, since
we need to curate the posts anyway.
Vlad
On M
FYI Vlad now has webmaster- level permissions on the forums too, and a
nice Hibernate Team badge.
Good luck, and try to not ban innocent users ;-)
We could try something like Akismet, but does someone know if there
are chances to make it work with our very old version of the forums?
I don't think
Is the idea that some other community project could develop their own
alternative "criteria API"?
I think that would be really interesting to encourage - or at least
not make it harder - for people to experiment in that direction.
But of course, if the cost is high for you maybe that's better
addr
Hi,
Someone on Twitter pointed out this issue:
https://hibernate.atlassian.net/browse/HHH-9764
I managed to add a test case using the Hibernate ORM Test Templates and the
issue is replicated.
The question is whether we should run the version check when loading
entities from the database. This iss
Thanks for pointing that out.
The robots.txt is in place https://docs.jboss.org/robots.txt.
But I couldn't find the sitemap.xml
According to Google:
https://support.google.com/webmasters/answer/156184?hl=en
The sitemap.xml is important if:
- Your site is really large
- Your site has a large arch
15 matches
Mail list logo