He is talking about native (sql) queries. If a user defines a native query
using his example column name MY_SUPER_AWESOME_COLUMN_NAME_CANT_ALWAYS_BE_USED,
then when we replace that because they deploy on to "database product X"
which limits identifier lengths to 10... he worries that the users que
Hi Max, could you make an example please?
Looks like you are interpreting Steve's email in a different way than me.
On 24 Jul 2015 21:43, "Max Rydahl Andersen" wrote:
> On 24 Jul 2015, at 16:48, Steve Ebersole wrote:
>
> > Do we want to consider automatically applying known database limits on
> >
+1
On 24 Jul 2015 15:54, "Steve Ebersole" wrote:
> Clarification... the issues scheduled for 5.0.0+ all need to be resolved
> *or* moved from 5.0.0+
>
> On Fri, Jul 24, 2015 at 7:32 AM Steve Ebersole
> wrote:
>
> > Well there is still a lot of issues scheduled for `5.0.0+`. Those would
> > all
Worth keeping these around anymore? They are woefully out of date.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
FWIW the check command failed, but then `rake preview` seems to run fine (I
can view the site locally). I guess the severity of this depends on what
check is meant to do...
On Sat, Jul 25, 2015 at 10:24 AM Steve Ebersole wrote:
> [sebersole@t540 in.relation.to] $ rake check
> rake aborted!
> Do
[sebersole@t540 in.relation.to] $ rake check
rake aborted!
Don't know how to build task 'check'
^^ expected? `rake setup` finished successfully. This next step failed
for me.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jb
