DISQUS

That's too bad it had to be changed. At least all of the good info is still there. I updated the post with the new links and new name.

It looks like http://disqus.com/ is a bit better at implementing the comments. Though I have noticed it takes over a minute before the comments shows and it doesn't keep me logged in.

Example: http://mtg.pyrodius.com/card/Taiga

I was thinking that if someone were to get ahold of the user table, they would know the salt used and with a lot of time and horsepower try many words with the salt. Hiding the salt in any way would create some kind of pattern, but I wouldn't know how much weaker that would make it. Guessing that this tactic might be used would probably be easier than getting ahold of a random salt.

I noticed another case I may have missed, so I edited the post to catch when the key may be a smallint.

Try running these 4 queries.


CREATE TABLE manila_area_tbl
(
area_no SERIAL,
area_name varchar(65) NOT NULL,
disp_flag char(1) NOT NULL default 1,
disp_no smallint NOT NULL,
del_flag char(1) NOT NULL default 0,
PRIMARY KEY (area_no)
) ;

CREATE INDEX disp_no ON manila_area_tbl (disp_no);

CREATE INDEX del_flag ON manila_area_tbl (del_flag);

ALTER SEQUENCE manila_area_tbl_area_no_seq RESTART WITH 25;

I removed the requirement for e-mail. I had no idea WordPress handled it so poorly since I was always logged in.

@kL
Thanks for the comment. I updated the post to cross out the NOT NULL part, I think I meant that only for the auto_increment part, but messed it up.

I'll check out the newer versions to see what's been changed. I was on 7.4.7.

Ah it would be COALESCE(log_deleted, 0) = 0 for MySQL

Thanks for the responses. I'll have to test out the performance of using OR in MySQL and see if it has similar performance loss.

It looks like that would only be an alternative for MSSQL since the ISNULL function only has one parameter for MySQL. I'll keep an eye out for something similar in MySQL.

Yeah I guess the parenthesis weren't needed, but the result of one query (SELECT) is going to the other (INSERT) so I'd probably still call it a subquery.

Additional note, even though it says ON DUPLICATE KEY, when using UNIQUE for one or more columns it will behave the same.

Thanks for the input, Brian. That is a great idea and works the same. I didn't think of adding the condition there.

Thanks for translating this to Spanish. I'm sure there are people that would understand it better that way.

Someone posted this on a link sharing site and there has been some discussion going on there. http://news.ycombinator.com/item?id=182529

I've noticed that WordPress Plugins have the ability to do some of what I would like. I'm not sure if they have revision histories or rollbacks since there wasn't a problem when I was updating.

I will have to look into how they are doing this.

The keg still lives on, despite our efforts to deplete it!

Some more ideas of ways to improve the data of the site.

Get an updated copy of the database. There are new cards out. Then reapply and document the procedure to get it to pretty MySQL tables.

There are currently 842 different Card Types since each different creature type is in that field. Break the creature type from the card type. Once that is done, it would be easier to do a groupby-searchby box like card rarity.

Split card color to a separate table and join it to the card table with a join table. Each card can have multiple colors and it will be easier to search for cards containing the color Red.

I've created an OpenID auth module as well. It will also use a post handler for the initial OpenID submission to the OpenID provider.

To implement the auth module, an additional table will be needed that joins user_ids with open_ids. The functions for retrieving that information will be included in the user class.

This is all the documentation you get for now.

I'm almost ready to throw out a g9. I've added folder support in the keys directory to help organize those. Also, for the larger projects, I've made the database connection follow the singleton design principle so that there won't be extraneous connections. So keep an eye out for this update.

DB tries to reinclude the mysql class file. Fix the include files function by writing the autoload thing.

getting the proper error messages to show up and moving that text to the language file.

To Do:

locate some of this stuff done and add it to the repository

Cookies kept me logged in properly now. All is working except the problem with the bad signature that only happens with http://videntity.org as the provider.

OpenID discussions mention it could be a problem with character encodings or GMP...

Getting an error that says "Session state not found". It happened after being logged in, but idle for a weekend.

I moved everything into the auth_routine and removed the post_handler to get it working properly. Still need to wait a while to double check, but should be fine.

Also, I need to get OpenID sessions to stay active with cookies. At the moment it is expecting a response from the provider and skipping the step where it sends a request to the provider since that part is in a post handler.

After all the fighting to get this to a better table schema, it increased the query I was trying to optimize from 23.0878 seconds to 0.0638 seconds. That's like 36,000% better!