Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think that most of the time when things (usernames or passwords) are being forced down to ASCII, it's because someone is afraid that more complex character sets will cause breakage in some unknown component. Whether this fear is justified or not is case dependent, but trying to verify that your entire stack really does Unicode correctly in all cases might be difficult. It's getting better every day, but you can still find problems with Unicode in some places.</p> <p>I personally keep my usernames and passwords all ASCII, and I even try not to use too much punctuation. One reason is that some input devices (like some mobile phones) make it kind of difficult to get to some of the more esoteric characters. Another reason is that I've more than once encountered a system that had no restrictions on the password contents, but then screwed up if you actually used something other than a letter or number.</p>
    singulars
    1. This table or related slice is empty.
    1. POUnicode in usernames (and passwords)?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMichael Kohne
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COSo basically most admin/developers are in this simply for the sake of being lazy and not wanting to support their users from different parts of the world. ;) However as far as phones go, I'm not aware of this particular project working well with them anyway, so it's kind of moot for me and this. I can see why you'd want to take the time to mention them though. Thanks for that.
      singulars
      1. PO
      1. USZydeco
    2. COI don't know it's that bad. These days lots of people are (finally!) starting to get their Unicode act together. Unfortunately, it's still way too easy to write applications that don't do Unicode, and there's a whole lot of old software from before Unicode that has to be updated. Frankly, I can't blame folks for trying to not run into any weird new edge conditions in the software they've deployed.
      singulars
      1. PO
      1. USMichael Kohne
    3. COOh, it's very bad. I blame developers and admins that can't see past the ends of their English-speaking noses. Forgive me for being forward with this, but remember "www" doesn't stand for "the English speakers only" - more like "World-wide" - which happens to include languages other than the one we're using here. To me, and others, "weird, new edge conditions" might very well include being limited to one language. Of course, I can't really blame you. There are a few countries full of people that think the only real language in the world is English, so why support anything else?
      singulars
      1. PO
      1. USZydeco
 

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