Once we have the code working for PostgreSQL, I think we should go on to implementing triggers for post number incrementing, et al.
But I still have to fix the filter first anyway,
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Once we have the code working for PostgreSQL, I think we should go on to implementing triggers for post number incrementing, et al.
But I still have to fix the filter first anyway,
The new back end.
I wonder if things were coded assuming Count(0) =0?
DX, I think my explanation still applies. I think the code will always set the post_number one too high, but after this happens once then future posts will follow in correct sequence.
msbelle, the sign-in problem was fixed (assuming there was only one sign-in problem). Last night my internet access died, so I didn't do any fixing beyond that. So there are still some known issues for me to fix.
I don't know offhand if all possible functionality has been tested yet.
edit for spelling....
No one post in the test board, please. I'm changing code so....
OK, I fixed a bunch of stuff. I'm going to exercise for a bit.
Can somebody(s) go to BBaBB on the test system, see what I did, and remind me what else needs to be done?
I'd like to help out, but I never got the confirmation email.
Daniel, I just sent it again, and activated the account. Let me know if you don't get it.
Maybe Daniel originally registered back when the confirmation email didn't have a "from" address? (which caused some spam filters to reject it)
Huh--I just noticed that nothing is in the user_timestamp field. Is this being used? Maybe the MySQL version this field defaults to Now()?
You can check out the table structures using the MySQL command line utility, tommyrot -- there are definitely defaults and restrictions therein.
Yeah, but I'm being lazy....
OK, at some point I'll have to check all the MySQL tables for defaults, as I think I missed another default for the bookmarks table.