Thank you so much. I was hoping you would ring in. What you're saying all matches what I'd expected.
So the things people like me do with SQL are either: 1) Design a system from scratch because holy crap we've got stuff and need to be able to find it, or 2) Take our existing heap of data and refine or maintain it.
The bare bones would be the ability to query the existing database directly instead of flapping my hands at an engineer every time I need a new cross-section of data. Predictably the bare bones of what is easy to *learn* is exactly the opposite.
Currently I have rudimentary write-only knowledge of SQL. I can set up fields and hook them together, and I understand about keys, and I know when something's normalized or not, and I might even be able to set up a form that you use to enter stuff in fields. (I also have similar experience with Access.)
Aaaand I might be able to manage a basic union retrieval command.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2011-02-15 10:44 pm (UTC)So the things people like me do with SQL are either:
1) Design a system from scratch because holy crap we've got stuff and need to be able to find it, or
2) Take our existing heap of data and refine or maintain it.
The bare bones would be the ability to query the existing database directly instead of flapping my hands at an engineer every time I need a new cross-section of data. Predictably the bare bones of what is easy to *learn* is exactly the opposite.
Currently I have rudimentary write-only knowledge of SQL. I can set up fields and hook them together, and I understand about keys, and I know when something's normalized or not, and I might even be able to set up a form that you use to enter stuff in fields. (I also have similar experience with Access.)
Aaaand I might be able to manage a basic union retrieval command.