DB With 2241 Tables

Content Programmers who've stayed in one job too long unwittingly setting company coding standards so where are we going? we're following you. 6. 52

Content You shouldn't use client javascript to access databases for several reasons (bad practice, security issues, etc) but if you really want to do this, here is an example: 748 var connection new Activexobject ("ADODB .Connection") ; var connectionstring "Data Source server; Initial Catalogcatalog ;User IDuser; Password connection. Open (connectionstring); new ActiveXObject ("ADODB. Recordset"); rs. Open ("SELECT FROM table", connection); rs.MoveFirst while(!rs.eof) document.writers.fields (1)); rs.movenext; rs. close; connection. close; A better way to connect to a sql server would be to use some server side language like PHP, Java, NET, among others. Client javascript should be used only for the interfaces. And there are rumors of an ancient legend about the existence of server javascript, but this is another story. ;) Share Edit Follow Flag edited Jun 24 '09 at 13:27 answered May 13 09 at 12:29 Fabio Vinicius Binder 12.5k 4 30 32

Oh honey, someone just turned database design into relationship advice and honestly? They're not wrong. The setup is *chef's kiss* – girl asks what you need for a good relationship, and this absolute legend responds with "PRIMARY KEYS" because apparently we're all just living in one giant relational database and nobody told us. For those blissfully unaware: primary keys are what keep your database tables from descending into chaos. They're unique identifiers that make sure every record is special and can be properly referenced – you know, like how you'd want to uniquely identify your significant other instead of accidentally texting the wrong person named "Alex" in your contacts. Without primary keys, your relationships (and your data) would be a hot mess of duplicates and confusion. So yeah, turns out good data integrity and good relationships have more in common than we thought. Who knew SQL was secretly a dating guru this whole time?

Content 112. 18 min. ago Good point but coders need to know that what they do isn't actually that hard. It just isn't and lots and lots of people either already know how to do what you do, or they could learn to do it as well within a very short window. - Vote Reply Give Award Share Report Save Follow (a) fromtheeast OP 7 min. ago I am guessing you know how to build an API, build the databases, and then build the deployment infrastructure (eg into AWS)? An actual coder would not make this comment. 4 1 S Reply Share Save Edit Follow ... 01 111 5 min. ago If I don't, I could learn in about 8 or 9 days. That's the truth. I will tell you another thing, what angers you about EM's comment is that you know the coding details are quite beside the point ... he's running things now and that's the main detail that matters. Vote S C Reply Give Award Share Report Save Follow

Content camelCase snake case Me made with mematic ProarammerHumor.io

That moment when your "quick fix" SQL query has been running for 10 seconds and you suddenly realize you forgot the WHERE clause. The hamster perfectly captures that split second of pure panic when you connect the dots - your simple update is now wreaking havoc on every single row in production. Time slows down as you frantically reach for Ctrl+C while simultaneously having an out-of-body experience where you see your entire career flash before your eyes. The backup you didn't make last week suddenly feels like a really critical life choice.