Sai Pullabhotla wrote:
Rick,
Thanks for the advice on using a CHECK constraint. It surely helps ensuring
the data integrity.
Otherwise, I think this is very basic feature that every one would like to
see, and it would help if Derby can handle this automatically using the
Computed/Generated c
Mark Thornton wrote:
Sai Pullabhotla wrote:
Rick,
Thanks for the advice on using a CHECK constraint. It surely helps
ensuring
the data integrity.
Otherwise, I think this is very basic feature that every one would
like to
see, and it would help if Derby can handle this automatically using the
Rick,
Thanks for the advice on using a CHECK constraint. It surely helps ensuring
the data integrity.
Otherwise, I think this is very basic feature that every one would like to
see, and it would help if Derby can handle this automatically using the
Computed/Generated columns or allowing UNIQU
Hi,
I'm seeing performance problems when running a query that left outer
joins to subqueries together. Each subquery returns 1000 rows and
takes under 1 sec to execute. The whole query returns 0 rows (as
expected) but takes 60 secs. The join is evaluated using nested loops,
so I assume the problem