OK, let's test it with JDBC:
import java.sql.*;
import org.h2.api.Trigger;
public class TestTrigger {
public static class T implements Trigger {
@Override
public void init(Connection conn, String schemaName, String
triggerName, String tableName, boolean before,
Yes, I made mistake when I was copying code. The class of course looks like
this: public class TriggerBeforeInsert implements Trigger. The rest is
unchanged.
W dniu niedziela, 4 sierpnia 2019 17:48:40 UTC+2 użytkownik Piotr napisał:
>
> I'm Trying to create an H2 Trigger which should trigger
Sure Evgenij. I'll be posting, thanks for the help. I just posted here
because want to know is there any specific H2 library change which is
affecting my impl. As I only touched the H2 library in my impl
On Monday, August 5, 2019 at 4:19:21 PM UTC+5:30, Evgenij Ryazanov wrote:
>
> If you have a
If you have a problem with some implementation of JPA it's better to post
your question on StackOverflow with appropriate tags or in some other place
where your question will be visible by many people familiar with JPA,
Hibernate and other related stuff.
I have no idea how to while a correct
Interesting that it even works in 197.
Env: Oracle JDK 8 and AmazonCorreto JDK 11.0.3, W10, Intellij
FYI I used orderby but didn't worked.
return createQuery((cb, root, query) -> {
List predicates = createCriteria(id, addrSearchParams, cb,
root);
Query q =
I assume you understand that order of results in queries without ORDER BY
can be changed again at any time. It's better to change tests in
order-independent way.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group
Yes, the results are same as like 198. I think finally I've to change the
200+ test cases due to this problem.
Thanks for the help Evgenij. I'm still searching...
On Monday, August 5, 2019 at 3:08:54 PM UTC+5:30, Evgenij Ryazanov wrote:
>
> Most likely the results will be the same as in
Most likely the results will be the same as in 1.4.199. But 1.4.199 is more
reliable in other areas.
You can also sort the results by your own in your test cases.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group
Thank you Evgenij,
Will test with 199. Lets see whats the result then. Unfortunately I cant
apply the order by clause, it will affect a lot on application. Will be
happy to see any other alternatives.
On Monday, August 5, 2019 at 2:40:20 PM UTC+5:30, Evgenij Ryazanov wrote:
>
> 1.4.197 and
1.4.197 and 1.4.198(199) are huge releases with a lot of changes.
BTW, don't use 1.4.198, this release has many regressions, it was replaced
with 1.4.199.
Some queries may return result in different orders on Java 7 and on later
versions. Some queries may change the order of results depending
Hi Noel,
Thanks for the reply. Why I'm curious, because it wasn't affected till
1.4.188 version without using order by clause. So is there any special
improvements after 188 to act like this.
On Monday, August 5, 2019 at 1:56:31 PM UTC+5:30, Noel Grandin wrote:
>
> Unless you are using an
Unless you are using an ORDER BY clause, the order of results is undefined
in SQL, so it can change at any time
>
>
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
Hi,
I'm getting the different result when upgraded to 1.4.198 version. While
till 1.4.188 the results are expected works correctly.
The below test fetch data for Id:1 having list of two members, the sequence
of member Id's in list is 3, 2. But which is 2, 3 in 1.4.198 that's why the
tests are
13 matches
Mail list logo
