Expansion on the potential issue at p. 23 (whether or not I apply it though) #41
Description
I noticed and used this change initially when going through p. 23: #29
I'm noticing with this fix, the status field is adjusted to a varchar(2). Is that okay? It looks like it'll still store the 2-char
I switched the code back to original text and it seems to work from my installation but the varchar(2) stayed a varchar(2), so it didn't fix what I was hoping to fix either. As I'm here to learn Django, I'm not sure if there's an issue going forward from here.
Maybe there were changes in the SQL interpretation of enumerated fields? Or something "different" between databases, though I'm using the SQLLite default.
More notes:
The original issue would've started at p. 20.
The white-on-black output at p. 24 shows
"status" varchar(10) NOT NULL,
... but with the change shows
"status" varchar(2) NOT NULL,