Куча полезной информации на сайте wiki.noljads.com.
Кросспост из Wordpress в ЖЖ.
Переименовать в базе данных collation с “latin1_swedish_ci” на “utf8_unicode_ci” не помогло, так что открутил назад.
А вот если закомментировать в файле wp-config.php две строчки, превратив
define('DB_CHARSET', 'utf8'); define('DB_COLLATE', '');
в
// define('DB_CHARSET', 'utf8'); // define('DB_COLLATE', '');
то все работает нормально.
P.S. Как выяснилось, в процессе перестановки collate туда-сюда, в части старых постов почему-то заглючили отдельные символы (тире и кавычки, хотя и не везде). Пришлось подправить вручную.
If you may configure something using Spring — never ever try to configure the same thing with Hibernate.
Sorry, Gavin.
The colleague of mine just got this from his IntelliJ IDEA 7.0.2:
At least it apologizes…
May someone explain me why the following HTML code is causing IE6 SP2 crash?
<html xmlns="http://www.w3.org/1999/xhtml"> <body> <table> <tr> <td> <table style="table-layout:fixed"> <col width="20"/> </table> </td> </tr> </table> </body> </html>
Bonus: CodeColorizer
There is something charming in those small things IDE developers make for us.
This week Mainsoft introduced a new source of information for all Grasshopper users: «The Grasshoppers» blog.
Although currently there is only one person actually blogging there, this is a promising step forward to developing a rich community of both Grasshopper users and developers.
By the way, it worth to take a look at full Grasshopper bloggers list.
Since CafePress is still lacking any kind of Mono project stuff, I decided to make one of my own.
There is nothing better than starting you morning with a good cup of Mono…
Another example of problem similar to hashCode() mutability is an option for broken «consistent with equals» contract imposed by implementation of java.util.TreeSet while implementing java.util.Comparator.
Actually, both of these cases (as well as a numerous others) are just an evidence of much wider problem - the requirement to follow some kind of contract various infrastructure implementations rely on and lack of ability to validate/impose such a constraints using existing IDEs and tools. The basic of this is the fact no IDE vendor can track an implementations of an infrastructure libraries existing (the best support feasible to achieve is Microsoft-style solution: an inspection for .Net framework libraries embedded into Visual Studio) and thus creating inspections “by reaction” will always loose the battle.
The best way to avoid the gap between software component and the inspections is to eliminate the “broken phone” between the software developer, the documentation developer and the inspections developer. This presents an «inspection by creator» paradigm - inspections are developed in parallel with a software component (and in ideal case by the the same software developer), embedded within the component, and shipped with it.
Summarizing the basic requirements for such a framework:
Upon meeting the two first requirements the last three can be easily accomplished by using existing standard mechanisms like annotations and attributes.
Imperva CTO, Amichai Shulman has launched his own security-oriented blog.
He moistly writes about enterprise security «metas», providing a lot of valuable background information resources. A must-read for any enterprise-level developer.
This is bilingual blog.
You may found it useful to read the entries separately based on their language.
