Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Since I read the Joel article and some other I18n articles I always kept a close eye to my character encoding; And it actually works if you do it consistantly. If you work in a company where it is standard to use UTF-8 and everybody knows this / does this it will work.</p> <p>Here some interesting articles (besides Joel's article) on the subject:</p> <ul> <li><a href="http://www.tbray.org/ongoing/When/200x/2003/04/06/Unicode" rel="noreferrer">http://www.tbray.org/ongoing/When/200x/2003/04/06/Unicode</a></li> <li><a href="http://www.tbray.org/ongoing/When/200x/2003/04/26/UTF" rel="noreferrer">http://www.tbray.org/ongoing/When/200x/2003/04/26/UTF</a></li> </ul> <p>A quote from the first article; Tips for using Unicode:</p> <ul> <li>Embrace Unicode, don't fight it; it's probably the right thing to do, and if it weren't you'd probably have to anyhow.</li> <li>Inside your software, store text as UTF-8 or UTF-16; that is to say, pick one of the two and stick with it.</li> <li>Interchange data with the outside world using XML whenever possible; this makes a whole bunch of potential problems go away.</li> <li>Try to make your application browser-based rather than write your own client; the browsers are getting really quite good at dealing with the texts of the world.</li> <li>If you're using someone else's library code (and of course you are), assume its Unicode handling is broken until proved to be correct.</li> <li>If you're doing search, try to hand the linguistic and character-handling problems off to someone who understands them.</li> <li>Go off to Amazon or somewhere and buy the latest revision of the printed Unicode standard; it contains pretty well everything you need to know.</li> <li>Spend some time poking around the Unicode web site and learning how the code charts work.</li> <li>If you're going to have to do any serious work with Asian languages, go buy the O'Reilly book on the subject by Ken Lunde.</li> <li>If you have a Macintosh, run out and grab Lord Pixel's Unicode Font Inspection tool. Totally cool.</li> <li>If you're really going to have to get down and dirty with the data, go attend one of the twice-a-year Unicode conferences. All the experts go and if you don't know what you need to know, you'll be able to find someone there who knows.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POAre you fluent in Unicode yet?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USfijter
    1. USfijter
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAre you fluent in Unicode yet?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COExcellent links and feedback. Thanks.
      singulars
      1. PO
      1. USAsh
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload