Hi,
Executing the following statements only returns records with num != NULL.
Is that the intended behavior?
CREATE TABLE yyy (num DECIMAL(7))
/
INSERT INTO yyy VALUES (NULL)
/
INSERT INTO yyy VALUES (1)
/
INSERT INTO yyy VALUES (5)
/
INSERT INTO yyy VALUES (NULL)
/
SELECT * FROM yyy WHERE
Hi,
Yes, this is how other databases work as well. The reason is that a
comparison with NULL results in NULL. And NOT NULL is also NULL. And NULL
means no match.
Regards,
Thomas
On Fri, Nov 14, 2014 at 9:08 AM, christoff.schm...@finaris.de wrote:
Hi,
Executing the following statements only
Hi,
As I wrote, you have two options: One workaround is to not upgrade to
version 1.3.176 if the database was created with an earlier version (use
whatever version you are already using). Another workaround is to export
the database file to a SQL script and re-create it.
Regards,
Thomas
On
Hi,
Well, most people would probably say Oracle has no bugs :-) It's just an
incompatibility. The ANSI SQL standard is relatively weak.
Regards,
Thomas
On Wed, Nov 12, 2014 at 8:39 PM, Pavel pgane...@gmail.com wrote:
Hello,
I noticed this in H2 database.
stat.execute(CREATE TABLE
Hi,
Could you post the complete stack trace please (including caused by)?
Regards,
Thomas
On Thu, Nov 13, 2014 at 10:32 AM, Duc Nguyen duc...@gmail.com wrote:
Recently i have been facing with many errors in which the temp blob
database file cannot be read, and read error exception thrown.
Hi,
I would be interested in the patch. Even thought, I can not guarantee that
it will be applied - I would like to keep the Column class as simple as
possible.
Regards,
Thomas
On Wed, Nov 12, 2014 at 8:57 PM, Pavel pgane...@gmail.com wrote:
Hello,
I have a patch which partially implements
Hi,
This is an internal API. You are not supposed to use the output of
TableFilter.getSelect().getSQL() and try to run it with another database.
The extra = sign is needed there.
Regards,
Thomas
On Tue, Nov 11, 2014 at 8:15 AM, Jiunn Jye Ng jiunn...@gmail.com wrote:
Hi All,
I am working on
Hi,
I think the PayPal option _is_ visible. You just need to scroll down a bit
in the main web page (http://h2database.com/html/main.html). Do you think
it should be on the top of the page, so you don't have to scroll down?
Regards,
Thomas
On Fri, Nov 14, 2014 at 1:30 PM, Arda Orhan
Hi Thomas,
Nope, i don't want it to be on the top of page, it should be on the
navigation menu.
Best Regards
Ali Arda Orhan
On Fri, Nov 14, 2014 at 2:40 PM, Thomas Mueller
thomas.tom.muel...@gmail.com wrote:
Hi,
I think the PayPal option _is_ visible. You just need to scroll down a bit
in
My users are starting to report similar errors to the ones seem by Rami.
They're apparently also caused when dropping, but this time it's tables
rather than schema. Here's a report from today...
Caused by: org.h2.jdbc.JdbcSQLException: General error:
java.lang.IllegalStateException: Chunk 6804
We have a product that has been using H2 for years. We had a major upgrade
of our code without changing the H2 version (1.3.174) and are running it at
scale for the first time. In the three months before upgrading the database
grew from about 1.5GiB to 2.0GiB. In the first two hours after
Hi,
That's strange. After running the Recover tool, could you post the
statistics part, which is the last part of the file? For an empty
database, this is:
Statistics
-- page count: 12, free: 0
-- page data bytes: head 125, empty 18612, rows 1743 (10% full)
-- data leaf 41%, 5 page(s)
Hi,
In H2 version 1.3.182 there were some changes in this area. If you could
use that version, that would be great.
I'm currently working on this area, ensuring that chunks are not
overwritten when they are still used. My guess is that there is something
wrong with the mechanism that detects
13 matches
Mail list logo