Logged In: YES
This has been fixed in the current CVS tree.
Currently passing sets.Set as a parameter works (not
everything is checked in, and it needs a little more work).
Reading SET columns still returns, due to the field type
returned by MySQL; see bug referenced above.
The bug has been verified, awaiting fix.
Clarification: Reading SET columns still returns a string of
comma-separated values, due to above-reference bug.
Solution: Though the field type seems to never be
FIELD_TYPE_SET, the field flag for sets (SET_FLAG) does
get set. I'm committing a fix for this soon so it will be in
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.