Frank Schönheit - Sun Microsystems Germany wrote:
Hello Barbara,
Now, with 2.4.1, the GUI is having a great deal of trouble with these
queries (at least sometimes). It tells me the query is too complex to be
edited with the GUI, or if it shows it, the NOT LIKE vanishes from the
condition leaving only '*/*' -- not at all what I want!
That sounds like worth an issue - care to submit one, with a small
sample database?
I never really
wanted that condition anyway, a simple IS EMPTY really ought to suffice.
If I edit the SQL, the query works OK.
It sounds like you're confused by the difference between empty strings
and NULL values. In the UI, both look the same, yet to the database
engine they're different things.
Try a
UPDATE <table_name> SET <field_name> = NULL WHERE <field_name> = ''
in Tools/SQL.
This will change all empty strings in your table to contain NULL, in
which case the IS EMPTY condition should be sufficient, again.
Thanks, Frank. The field was originally really NULL (as in the new
records) but the copy/import process changed it to two blanks, and the
TRIM left it as an empty string instead of a NULL. Thanks for the SQL to
fix it. The other oddity is that the true NULL fields, since they aren't
strings, don't satisfy the NOT LIKE condition on a string. But I'll be
glad to get back to the IS EMPTY only, and I'll remember this if I need
it for my next database reset.
I'll set up a test database for the GUI issue and submit it. Should I do
one for the text padding, too, or is that already in there? (I should
have done that last year, but got too swamped to pursue it.)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
