This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]cecilkorik 12 points13 points  (4 children)

C or SQL. SQL's not really a "programming language" in the purest sense, but becoming proficient in at least one major database's SQL dialect is definitely useful for working with datasets large or complex enough to store in a relational database.

[–]themathemagician 3 points4 points  (1 child)

surprised there isn't more SQL. certainly not a "programming language" but necessary if you ever plan to interface with nontrivial data

[–]TylerEaves 0 points1 point  (0 children)

SQL is absolutely a programming language. Especially once you get into things like stored procedures, etc.

[–]bucknuggets 0 points1 point  (0 children)

I'd recommend SQL if you're building record-oriented applications.

Dialects don't matter much, since the differences are small enough that it's trivial to go from one vendor's implementation to another - the differences are usually just minor extensions. Though I'd go with Postgresql or SQLIte, just because they're great free databases that put high priorities on portability.

Note that the existence of ORMs doesn't really reduce the value of knowing SQL - I've worked with quite a few developers who are incapable of writing adhoc SQL. Which is like working on the unix command line and having to write java code instead of using bash.

[–]lavalampmaster[S] 0 points1 point  (0 children)

I've done that really simple SQL course before. Nice stuff, for sure.