Databases
StackOverflow2013
Usersdbo
UScircular-ruin
 

Note that there are some explanatory texts on larger screens.

plurals
  1. UScircular-ruin
    primarykey
    data
    text
    plurals
    1. PO
      singulars
      1. PTAnswer
    2. POData.ByteString.Lazy.Char8 newline conversion on Windows---is the documentation misleading?
      singulars
      1. PTQuestion
    3. PO
      singulars
      1. PTAnswer
    1. PORead a unicode file in python which declares its encoding in the same way as python source
      singulars
      1. PTQuestion
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhat are Haskell's monad transformers in categorical terms?
      1. UScircular-ruin
      1. VTFavorite
    1. COWow! That would be very kind, although it's really not necessary---I can try to roll my own, although doubtless my efforts would not be as good as those of a Master such as yourself :-). If you are thinking of doing an implementation, it strikes me that ideally one could solve the problem for more than just strings; depending on the implementation route, you probably ought to be able to `Atomize' any type with Eq and Cmp or with Eq and a hash function.
      singulars
      1. POComparison of atom libraries for Haskell, e.g. simple-atom and stringtable-atom
      1. UScircular-ruin
    2. CO@PiotrDobrogost for the UTF8 decoding thing, you're right. It makes more sense to think about it the way you say (error if you see any bytes above `\x7f` unless you've seen the BOM, o'wise decode), but on the other hand I think that what I said (first decode, then error if you get any decode errors or if the result contains unicode chars above `\u7f`) is equivalent, and was as it happens the way I was thinking of things. BTW, would you like to see my Python code for this? (It's actually not 100% faithful to the algo above in that my code does recognize UTF16 BOMs, unlike python's interpreter).
      singulars
      1. PO
      1. UScircular-ruin
    3. CO@PiotrDobrogost: "Unless you have seen the UTF-8 BOM, generate an error message if you see any non-ASCII characters". I think this is correct as written. The rule is: if you (a) see a non-ASCII character and (b) you have not seen a UTF-8 BOM, then you should generate an error. (If you see a non ASCII character but did see a UTF-8 BOM, then you don't make an error message; and obviously if all the characters are ASCII you don't make an error message.) Hope this clarifies things. Please ask more questions if I'm still being unclear and/or it looks like I am really mistaken here.
      singulars
      1. PO
      1. UScircular-ruin
 

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