public interface Row2<T1,T2> extends Row
2
Note: Not all databases support row value expressions, but many row value expression operations can be simulated on all databases. See relevant row value expression method Javadocs for details.
Modifier and Type | Method and Description |
---|---|
Condition |
eq(Field<T1> t1,
Field<T2> t2)
Compare this row value expression with another row value expression for
equality
Row equality comparison predicates can be simulated in those databases
that do not support such predicates natively:
(A, B) = (1, 2) is equivalent to
A = 1 AND B = 2 |
Condition |
eq(Row2<T1,T2> row)
Compare this row value expression with another row value expression for
equality
Row equality comparison predicates can be simulated in those databases
that do not support such predicates natively:
(A, B) = (1, 2) is equivalent to
A = 1 AND B = 2 |
Condition |
eq(T1 t1,
T2 t2)
Compare this row value expression with another row value expression for
equality
Row equality comparison predicates can be simulated in those databases
that do not support such predicates natively:
(A, B) = (1, 2) is equivalent to
A = 1 AND B = 2 |
Condition |
equal(Field<T1> t1,
Field<T2> t2)
Compare this row value expression with another row value expression for
equality
Row equality comparison predicates can be simulated in those databases
that do not support such predicates natively:
(A, B) = (1, 2) is equivalent to
A = 1 AND B = 2 |
Condition |
equal(Row2<T1,T2> row)
Compare this row value expression with another row value expression for
equality
Row equality comparison predicates can be simulated in those databases
that do not support such predicates natively:
(A, B) = (1, 2) is equivalent to
A = 1 AND B = 2 |
Condition |
equal(T1 t1,
T2 t2)
Compare this row value expression with another row value expression for
equality
Row equality comparison predicates can be simulated in those databases
that do not support such predicates natively:
(A, B) = (1, 2) is equivalent to
A = 1 AND B = 2 |
Field<T1> |
field1()
Get the first field
|
Field<T2> |
field2()
Get the second field
|
Condition |
in(Collection<? extends Row2<T1,T2>> rows)
Compare this row value expression with a set of row value expressions for
equality
Row IN predicates can be simulated in those databases that do not support
such predicates natively:
(A, B) IN ((1, 2), (3, 4)) is
equivalent to ((A, B) = (1, 2)) OR ((A, B) = (3, 4)) , which
is equivalent to (A = 1 AND B = 2) OR (A = 3 AND B = 4) |
Condition |
in(Row2<T1,T2>... rows)
Compare this row value expression with a set of row value expressions for
equality
Row IN predicates can be simulated in those databases that do not support
such predicates natively:
(A, B) IN ((1, 2), (3, 4)) is
equivalent to ((A, B) = (1, 2)) OR ((A, B) = (3, 4)) , which
is equivalent to (A = 1 AND B = 2) OR (A = 3 AND B = 4) |
Condition |
ne(Field<T1> t1,
Field<T2> t2)
Compare this row value expression with another row value expression for
non-equality
Row non-equality comparison predicates can be simulated in those
databases that do not support such predicates natively:
(A, B) <> (1, 2) is equivalent to
NOT(A = 1 AND B = 2) |
Condition |
ne(Row2<T1,T2> row)
Compare this row value expression with another row value expression for
non-equality
Row non-equality comparison predicates can be simulated in those
databases that do not support such predicates natively:
(A, B) <> (1, 2) is equivalent to
NOT(A = 1 AND B = 2) |
Condition |
ne(T1 t1,
T2 t2)
Compare this row value expression with another row value expression for
non-equality
Row non-equality comparison predicates can be simulated in those
databases that do not support such predicates natively:
(A, B) <> (1, 2) is equivalent to
NOT(A = 1 AND B = 2) |
Condition |
notEqual(Field<T1> t1,
Field<T2> t2)
Compare this row value expression with another row value expression for
non-equality
Row non-equality comparison predicates can be simulated in those
databases that do not support such predicates natively:
(A, B) <> (1, 2) is equivalent to
NOT(A = 1 AND B = 2) |
Condition |
notEqual(Row2<T1,T2> row)
Compare this row value expression with another row value expression for
non-equality
Row non-equality comparison predicates can be simulated in those
databases that do not support such predicates natively:
(A, B) <> (1, 2) is equivalent to
NOT(A = 1 AND B = 2) |
Condition |
notEqual(T1 t1,
T2 t2)
Compare this row value expression with another row value expression for
non-equality
Row non-equality comparison predicates can be simulated in those
databases that do not support such predicates natively:
(A, B) <> (1, 2) is equivalent to
NOT(A = 1 AND B = 2) |
Condition |
notIn(Collection<? extends Row2<T1,T2>> rows)
Compare this row value expression with a set of row value expressions for
equality
Row NOT IN predicates can be simulated in those databases that do not
support such predicates natively:
(A, B) NOT IN ((1, 2), (3, 4)) is equivalent to
NOT(((A, B) = (1, 2)) OR ((A, B) = (3, 4))) , which is
equivalent to NOT((A = 1 AND B = 2) OR (A = 3 AND B = 4)) |
Condition |
notIn(Row2<T1,T2>... rows)
Compare this row value expression with a set of row value expressions for
equality
Row NOT IN predicates can be simulated in those databases that do not
support such predicates natively:
(A, B) NOT IN ((1, 2), (3, 4)) is equivalent to
NOT(((A, B) = (1, 2)) OR ((A, B) = (3, 4))) , which is
equivalent to NOT((A = 1 AND B = 2) OR (A = 3 AND B = 4)) |
Condition |
overlaps(Field<T1> t1,
Field<T2> t2)
Check if this row value expression overlaps another row value expression
The SQL standard specifies a temporal
OVERLAPS predicate,
which comes in two flavours:
(DATE, DATE) OVERLAPS (DATE, DATE)
(DATE, INTERVAL) OVERLAPS (DATE, INTERVAL)
jOOQ also supports arbitrary 2-degree row value expression comparisons,
by simulating them as such
-- This predicate
(A, B) OVERLAPS (C, D)
-- can be simulated as such
(C <= B) AND (A <= D)
|
Condition |
overlaps(Row2<T1,T2> row)
Check if this row value expression overlaps another row value expression
The SQL standard specifies a temporal
OVERLAPS predicate,
which comes in two flavours:
(DATE, DATE) OVERLAPS (DATE, DATE)
(DATE, INTERVAL) OVERLAPS (DATE, INTERVAL)
jOOQ also supports arbitrary 2-degree row value expression comparisons,
by simulating them as such
-- This predicate
(A, B) OVERLAPS (C, D)
-- can be simulated as such
(C <= B) AND (A <= D)
|
Condition |
overlaps(T1 t1,
T2 t2)
Check if this row value expression overlaps another row value expression
The SQL standard specifies a temporal
OVERLAPS predicate,
which comes in two flavours:
(DATE, DATE) OVERLAPS (DATE, DATE)
(DATE, INTERVAL) OVERLAPS (DATE, INTERVAL)
jOOQ also supports arbitrary 2-degree row value expression comparisons,
by simulating them as such
-- This predicate
(A, B) OVERLAPS (C, D)
-- can be simulated as such
(C <= B) AND (A <= D)
|
internalAPI
@Support Condition equal(Row2<T1,T2> row)
Row equality comparison predicates can be simulated in those databases
that do not support such predicates natively:
(A, B) = (1, 2)
is equivalent to
A = 1 AND B = 2
@Support Condition equal(T1 t1, T2 t2)
Row equality comparison predicates can be simulated in those databases
that do not support such predicates natively:
(A, B) = (1, 2)
is equivalent to
A = 1 AND B = 2
@Support Condition equal(Field<T1> t1, Field<T2> t2)
Row equality comparison predicates can be simulated in those databases
that do not support such predicates natively:
(A, B) = (1, 2)
is equivalent to
A = 1 AND B = 2
@Support Condition eq(Row2<T1,T2> row)
Row equality comparison predicates can be simulated in those databases
that do not support such predicates natively:
(A, B) = (1, 2)
is equivalent to
A = 1 AND B = 2
@Support Condition eq(T1 t1, T2 t2)
Row equality comparison predicates can be simulated in those databases
that do not support such predicates natively:
(A, B) = (1, 2)
is equivalent to
A = 1 AND B = 2
@Support Condition eq(Field<T1> t1, Field<T2> t2)
Row equality comparison predicates can be simulated in those databases
that do not support such predicates natively:
(A, B) = (1, 2)
is equivalent to
A = 1 AND B = 2
@Support Condition notEqual(Row2<T1,T2> row)
Row non-equality comparison predicates can be simulated in those
databases that do not support such predicates natively:
(A, B) <> (1, 2)
is equivalent to
NOT(A = 1 AND B = 2)
@Support Condition notEqual(T1 t1, T2 t2)
Row non-equality comparison predicates can be simulated in those
databases that do not support such predicates natively:
(A, B) <> (1, 2)
is equivalent to
NOT(A = 1 AND B = 2)
@Support Condition notEqual(Field<T1> t1, Field<T2> t2)
Row non-equality comparison predicates can be simulated in those
databases that do not support such predicates natively:
(A, B) <> (1, 2)
is equivalent to
NOT(A = 1 AND B = 2)
@Support Condition ne(Row2<T1,T2> row)
Row non-equality comparison predicates can be simulated in those
databases that do not support such predicates natively:
(A, B) <> (1, 2)
is equivalent to
NOT(A = 1 AND B = 2)
@Support Condition ne(T1 t1, T2 t2)
Row non-equality comparison predicates can be simulated in those
databases that do not support such predicates natively:
(A, B) <> (1, 2)
is equivalent to
NOT(A = 1 AND B = 2)
@Support Condition ne(Field<T1> t1, Field<T2> t2)
Row non-equality comparison predicates can be simulated in those
databases that do not support such predicates natively:
(A, B) <> (1, 2)
is equivalent to
NOT(A = 1 AND B = 2)
@Support Condition in(Collection<? extends Row2<T1,T2>> rows)
Row IN predicates can be simulated in those databases that do not support
such predicates natively: (A, B) IN ((1, 2), (3, 4))
is
equivalent to ((A, B) = (1, 2)) OR ((A, B) = (3, 4))
, which
is equivalent to (A = 1 AND B = 2) OR (A = 3 AND B = 4)
@Support Condition in(Row2<T1,T2>... rows)
Row IN predicates can be simulated in those databases that do not support
such predicates natively: (A, B) IN ((1, 2), (3, 4))
is
equivalent to ((A, B) = (1, 2)) OR ((A, B) = (3, 4))
, which
is equivalent to (A = 1 AND B = 2) OR (A = 3 AND B = 4)
@Support Condition notIn(Collection<? extends Row2<T1,T2>> rows)
Row NOT IN predicates can be simulated in those databases that do not
support such predicates natively:
(A, B) NOT IN ((1, 2), (3, 4))
is equivalent to
NOT(((A, B) = (1, 2)) OR ((A, B) = (3, 4)))
, which is
equivalent to NOT((A = 1 AND B = 2) OR (A = 3 AND B = 4))
@Support Condition notIn(Row2<T1,T2>... rows)
Row NOT IN predicates can be simulated in those databases that do not
support such predicates natively:
(A, B) NOT IN ((1, 2), (3, 4))
is equivalent to
NOT(((A, B) = (1, 2)) OR ((A, B) = (3, 4)))
, which is
equivalent to NOT((A = 1 AND B = 2) OR (A = 3 AND B = 4))
@Support Condition overlaps(T1 t1, T2 t2)
The SQL standard specifies a temporal OVERLAPS
predicate,
which comes in two flavours:
(DATE, DATE) OVERLAPS (DATE, DATE)
(DATE, INTERVAL) OVERLAPS (DATE, INTERVAL)
jOOQ also supports arbitrary 2-degree row value expression comparisons,
by simulating them as such
-- This predicate
(A, B) OVERLAPS (C, D)
-- can be simulated as such
(C <= B) AND (A <= D)
@Support Condition overlaps(Field<T1> t1, Field<T2> t2)
The SQL standard specifies a temporal OVERLAPS
predicate,
which comes in two flavours:
(DATE, DATE) OVERLAPS (DATE, DATE)
(DATE, INTERVAL) OVERLAPS (DATE, INTERVAL)
jOOQ also supports arbitrary 2-degree row value expression comparisons,
by simulating them as such
-- This predicate
(A, B) OVERLAPS (C, D)
-- can be simulated as such
(C <= B) AND (A <= D)
@Support Condition overlaps(Row2<T1,T2> row)
The SQL standard specifies a temporal OVERLAPS
predicate,
which comes in two flavours:
(DATE, DATE) OVERLAPS (DATE, DATE)
(DATE, INTERVAL) OVERLAPS (DATE, INTERVAL)
jOOQ also supports arbitrary 2-degree row value expression comparisons,
by simulating them as such
-- This predicate
(A, B) OVERLAPS (C, D)
-- can be simulated as such
(C <= B) AND (A <= D)
Copyright © 2013. All Rights Reserved.