Some DB fields are nullable, like member.address1. This is causing me a problem with the new template thing, so I'm planning to make all fields in the DB non-null. Nulls are problematic in DB theory, anyway, so I imagine this will make things work better all around. But I wanted to let you guys know in case you had any objections. When I get it done, I'll post a script to update your databases.
Well, I started work on this, but it's going to take longer than I have this week. There are some required nulls in booking and possibly in some of the lookup and other code. The DB schema needs more work than I thought it did. For now, I'm just going to make the fields in member not null so I can keep working on the problem at hand. Here's the SQL:
ALTER TABLE member
MODIFY `address1` varchar(128) NOT NULL,
MODIFY `address2` varchar(128) NOT NULL,
MODIFY `city` varchar(50) NOT NULL,
MODIFY `state` char(2) NOT NULL,
MODIFY `zip` mediumint(9) NOT NULL,
MODIFY `zip_ext` smallint(6) NOT NULL,
MODIFY `home_phone` varchar(15) NOT NULL,
MODIFY `work_phone` varchar(15) NOT NULL,
MODIFY `email` varchar(128) NOT NULL,
MODIFY `school_grade` varchar(10) NOT NULL,
MODIFY `school_teacher` varchar(50) NOT NULL;
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.