First of all, thanks for all your suggestions.
They were of two classes:
1. use different data representation (special constant from column domain
instead of NULL)
This is possible, of course, but it makes data model less portable and
requires changes in database abstraction layer of application
"Cestmir Hybl" <[EMAIL PROTECTED]> writes:
>> In fact, I need to filter by expression ((A is null) or (A > const)).
I wonder whether you shouldn't reconsider your data representation.
Perhaps the condition you are using "null" for would be better
represented by setting A to infinity. (The float a
On Thu, Oct 30, 2003 at 12:34:15 +0100,
Cestmir Hybl <[EMAIL PROTECTED]> wrote:
> Are you seeing this question as totally off-topic in this list, or there is
> really no one who knows something about indexing "is null" bits in postgres?
There was some talk about IS NULL not being able to use ind
Are you seeing this question as totally off-topic in this list, or there is
really no one who knows something about indexing "is null" bits in postgres?
Regards
CH
> Hi,
>
> suppose, for simplicity, there is a table with index like this:
>
> create table TABLE1 (
> A integer
> );
> create inde
