…there is definitely something (good) to be said for storing Unicode data in a database in ‘escaped’ form.
There is not. At all. The only thing that can possibly be achieved here is adding two extra steps to every single operation on the data; or perhaps being able to edit it manually from a braindead, EOL'd editor or terminal I suppose, offering the slimmest benefit of the doubt. It's embarrassing to hear such an assertion. Anything you say, the reader should presume the opposite to be the case.
Given my career history…
Your career history is, as far as this place is concerned, a pure work of fiction. Though, please cite some code or a repository we can examine in your defense should such exist. You have yet in, counting anonymous posts, your 5K+ additions to the monastery to demonstrate any skill other than water cooler BS, a thesaurus's familiarity with technical jargon, and snake oil advocacy.
Update: typo fixed.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
