I am creating a table using the result of an embedded py function.

The result of the function is a dictionary composed of numpy arrays.

The function and the CREATE TABLE work well. Inside the arrays of the dictionary, I have a few np.nan values, they seem to be recognized by monet during the creation of the table. In fact, when I query the whole table, I can see ‘null’ in the proper places.

But if I try to compare against these null values, I get nothing (SELECT * FROM table where field is null).

After a few trials, it seems to me that monet understands that np.nan is a NULL value, but then when it inserts the value into the table the internal representation (?) is somewhat different form a ‘normal’ NULL value.

Any suggestion?

Thanks, 

Stefano