SQL Language

[Aimster]

Have to learn it for work.

 

[2Xtreme21]

How intense? It's not hard for basic tasks.

 

[Deeko]

Not hard, but annoying and boring.

 

[Aimster]

I have to be able to write queries.

 

[theflyingpig]

Looks like you're going to be looking for new work.

 

[dfuze]

It can be easy or hard, depending on the type and depth of the queries.

 

[HardcoreRobot]

programming forum

 

[2Xtreme21]

Originally posted by: Aimster
I have to be able to write queries.

Do you understand the relational model?

 

[Capt Caveman]

Writing a simple query against a single table is easy. When you add conditions and joins to other tables is where it can get more difficult. Are you familiar with basic relational database table structure?

 

[ivan2]

not hard if you are going to use it in a daily basis, best to learn it in practices.

Also, against what database? There are some differences in Transact and Oracle.

 

[acheron]

So I get back from going to the ATM machine (where I put in my PIN number), and now I'm here reading ATOT Off Topic on my LCD display, and here's a post about the SQL language.

 

[Capt Caveman]

nvm

 

[nakedfrog]

What others said, just getting it to insert/update/select data is pretty simple, but you can also do some really complex stuff.

 

[theflyingpig]

Originally posted by: acheron
So I get back from going to the ATM machine (where I put in my PIN number), and now I'm here reading ATOT Off Topic on my LCD display, and here's a post about the SQL language.

I see what you did there you clever guy you.

 

[GeekDrew]

Writing statements in SQL is trivially easy, IMHO. Understanding how the data you are working with is modeled in the database with which you are currently working: sometimes not so easy.

 

[amdskip]

select * where userSQLknowledge > 0

 

[GeekDrew]

Originally posted by: amdskip
select * where userSQLknowledge > 0

Invalid column name 'userSQLknowledge'.
Must specify table to select from.

 

[Drakkon]

Its easier than Chinese but harder than Spanish

 

[torpid]

Easy to learn, difficult to master.

 

[L1FE]

Depends a lot on the database you're using, complexity of what needs to be done, and the amount of data you'll be manipulating. It's easy to write garbage SQL on a small data set and have that perform reasonably fast. Add in a few million/billion more rows, thousands more users, and you'll find that full table scans, holding records for update, row/table locks can all bring a production box to its knees. That being said, for the most basic of basic queries where you don't care about performance, it's ridiculously easy to learn.

 

[slsmnaz]

having recently done it myself (with no prior exposure) I will say the basic queries have become much easier. I got a SQL for beginners book and messed around in our dev environment trying many of the commands out. I still keep the book on my desk for reference but don't use it very often.

 

[MrPickins]

Originally posted by: dph1077
It can be easy or hard, depending on the type and depth of the queries.

Originally posted by: torpid
Easy to learn, difficult to master.

These.

 

[yllus]

Originally posted by: GeekDrew

Originally posted by: amdskip
select * where userSQLknowledge > 0

Invalid column name 'userSQLknowledge'.
Must specify table to select from.

Burn.

 

[PricklyPete]

It is by far one of the easiest "languages" to learn in my humble opinion if you have any concept of how a database is designed/works. The key is visualizing how the system will be handling the data you are processing and that will hugely benefit your codes efficiency.

 

[PricklyPete]

Originally posted by: Aimster
I have to be able to write queries.

If that is all you have to do...than a half hour tutorial is all you need.