Back
required attribute blank
I have several documents saved in 1.3.7 where a required attribute is blank. I'm not sure how the value got to be blank in my code, but I am also wondering even if I had a bug where my code attempted to save that, how did appwrite manage to carry out the save and not reject the whole createdocument/updatedocument operation?
TL;DR
The user is experiencing an issue with a required attribute being blank in their code. They speculate that the attribute was set to be required before any data was added and wonder if it is still possible for it to be an empty string. They also consider the possibility that the attribute became required after the data was added. The user is puzzled as to how the value became blank in their code and questions how Appwrite allowed the save operation to be carried out without rejecting it.
Solution: It is suggested to check the code to see how the attribute is being handled and if any bugs might be causing it to be saved as blank. Additionally, it is 
maybe it was made required after the fact. maybe it's an empty string rather than null
I never edited the attribute if that’s what you mean. It was set to be required before any data was added (the whole schema had been migrated from another instance). It says 0/36 for these blank ones. Could that still be an empty string?
yes, it could be an empty string
