See hidden discussions | Win great prizes | Get free support
I'd recommend understanding how relational databases work and the concepts behind it, and then the actual syntax and scripting.In its purest form?
Is it fun? Exciting?
Details, details I need moar!
That does sound like fun.I find it fun, I have always worked with databases so I might say, I don't have experience in anything else different. There is more to it than just select * from table; it gets fun when you have to optimise slow queries and using complex functions.
You almost need to work in an environment where you use a lot of data to really appreciate SQL.
Not much gaming these days unfortunately.Hey bro what's happening?!?
That sounds exhaustive and complex.My favourite part is using Postgres to generate GUID IDs but for that to happen I need an extension enabled but for that to happen on Azure I need super user access which means code first deployments (EF) require super user credentials...
Whereas with MSSQL you don't. But you have to pay a lot for this basic luxury.
That sounds exhaustive and complex.
What is a GUID ID?
Oh no, that's not good Always make time to play doesn't necessarily have to be gaming tho. Could also just be kicking a ball back at you off a wall.Not much gaming these days unfortunately.
So on the SQL side, I work for a really big IT company and we have tons of SQL only guys. Some are DBA's but others are just SQL guys.
They pull out reports when requested and fix the odd small problem from time to time.
So really I think it comes down to the size of the company, the bigger the staff the more specialized people become.
Why specifically would one use postgres to generate GUID's?GUID = Global Unique Identifier. Looks like this: e65fa27d-c44a-4f1f-9a0f-cdee0fce3b36
So instead of using a numeric value for an ID (Primary Key) you use those. Why would you do this? Various reasons. Why wouldn't you do this? Various reasons.