Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>Longevity</p> </blockquote> <p>No one can predict the future, but</p> <ul> <li>OCaml and Haskell have been surving well for a number of years, which bodes well for their future</li> <li>when F# ships with VS2010, MS will have legal obligations to support it for at least 5 years</li> </ul> <blockquote> <p>Practicality</p> </blockquote> <p>Perf: I don't have enough first-hand experience with Haskell, but based on second-hand and third-hand info, I think OCaml or F# are more pragmatic, in the sense that I think it is unlikely you'll be able to get the same run-time perf in Haskell that you do in OCaml of F#.</p> <p>Libraries: Easy access to the .Net Framework is a huge benefit of F#. You can view it as being "tied to this bulky thing" if you like, but don't forget that "you have access to a huge bulky library of often incredibly useful stuff". The 'connectivity' to .Net is one of the big selling points for F#. F# is younger and so has fewer third-party libraries, but there is already e.g. <a href="http://fscheck.codeplex.com/" rel="nofollow noreferrer">FsCheck</a>, <a href="http://www.quanttec.com/fparsec/" rel="nofollow noreferrer">FParsec</a>, <a href="http://code.google.com/p/fake/" rel="nofollow noreferrer">Fake</a>, and a bunch of others, in addition to the libraries "in the box" on .Net.</p> <p>Tooling: I don't have enough personal experience to compare, but I think the VS integration with F# is superior to anything you'll find for OCaml/Haskell today (and F# will continue to improve a bit here over the next year).</p> <p>Change: F# is still changing as it approaches its first supported release in VS2010, so there are some breaking changes to language/library you may have to endure in the near future.</p> <blockquote> <p>Well Designed</p> </blockquote> <p>Haskell is definitely beautiful and consistent. I don't know enough OCaml but my hunch is it is similarly attractive. I think that F# is 'bigger' than either of those, which means more dusty corners and inconsistencies (largely as a result of mediating the impedence mismatch between FP and .Net), but overall F# still feels 'clean' to me, and the inconsistencies that do exist are at least well-reasoned/intentioned.</p> <blockquote> <p>Overall</p> </blockquote> <p>In my opinion you will be in 'good shape' knowing any of these three languages well. If you know a big long-term project you want to use it for, one may stand out, but I think many of the skills will be transferable (more easily between F# and OCaml than to/from Haskell, but also more easily among any of these three than with, say, Java).</p>
    singulars
    1. This table or related slice is empty.
    1. POShould I learn Haskell or F# if I already know OCaml?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBrian
    1. USBrian
    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. 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. COWell the thing about being tied to the big bulky .NET, is that it forces you to bundle with it on purpose, instead of only selectively including the libraries you use.
      singulars
      1. PO
      1. USUnknown
    2. COWell, technically F# forces you to bundle .NET but in reality it will already be there before you. It is kind of like saying that it forces you to bundle Windows. Also, if you use Mono, they have a tool that lets you select only the functionality you are using. This is useful on the Mac where you include the supporting libraries into an app bundle (Mono is likely not already installed).
      singulars
      1. PO
      1. USJustin
 

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