If your working with Magento and have to move an installation, you will want to make sure it’s locally installed PEAR repository is updated as well. It stores a bunch of first install paths in a serialized PHP file. Instead of manually editing them, you can simply run this from the root install of your Magento:
./pear mage-setup
That should update everything to work as expected for updates and the like.
I came across this today: Working With Default Constraints
Basically, if you script any sort of table changes in MSSQL you will eventually need to use this code. In MSSQL’s infinite wisdom they made default values on NOT NULL columns occasionally have a mysterious constraint. Ordinarily, constraints on fields on tables are easily found in INFORMATION_SCHEMA.TABLE_CONSTRAINTS; but, these particular constraints are hidden for whatever reason.
This makes removing them programmatically very difficult, since they insist on putting a timestamp/guid on the end of each auto-generated default constraint. SO, this useful page on the MSDN provides a way to query the actual name of the constraint given the table name and column name. This, allowing you to remove it before you do something completely crazy like delete the column.
Of course, if your not in to scripting your database migrations then you can just use Management Studio and delete the column.
Basically it reads the mbox file and uploads it to the imap server. Simple and useful for systems where there are not alot of users and you just happen to know their passwords.
