• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

SQL Language

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?
 
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.
 
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.
 
What others said, just getting it to insert/update/select data is pretty simple, but you can also do some really complex stuff.
 
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.
Click to expand...
I see what you did there you clever guy you.
 
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.
 
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.
 
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.
 
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.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top