coding-style

When it comes to column order in DB tables, are there any standards or at least best practices? Here's a handmade convention that I follow: primary key (i.e. id ); unique columns (i.e. email , ssn ); foreign keys (i.e. article ); columns holding user generated data (i.e. first_name , last_name ); columns holding system generated data; non-boolean (i.e. password_hash ); boolean (i.e. deleted , verified ) timestamp columns (i.e. created_at ); These leave many questions unanswered, though, so I'd like to hear your thoughts. Patrick Karcher In short, you've stated the standard conventions well and

Our team works with Visual Studio 2017 Professional. I've been trying to unify the Code Style across the team and apparently the industry standard right now is to use .editorconfig files. Even Visual Studio in it's settings windows suggests to use that configuration file and links to a useful page on how to write an editorconfig file. but I don't want to write all the settings that I already have configured in VS by hand. I would like a tool that exports those settings as a .editorconfig file to distribute them. I haven't been able to find any tool to do just that so I thought on righting it

I'm curious as to how often experienced Haskell programmers really use type inference in practice. I often see it praised as an advantage over the always-explicit declarations needed in certain other languages, but for some reason (perhaps just because I'm new) it "feels" right to write a type signature just about all the time... and I'm sure in some cases it really is required. Can some experienced Haskellers (Haskellites? Haskellizers?) provide some input? It's still an advantage, even if you write type signatures, because the compiler will catch type errors in your functions. I usually

This is more of a stylistic question than anything else. Given the following piece of code: case e1 of (* datatype type_of_e1 = p1 | p2 *) p1 => case e11 of (* datatype type_of_e11 = NONE | SOME int *) NONE => expr11 | SOME v => expr12 v | p2 => case e21 of (* datatype type_of_e21 = NONE | SOME string *) NONE => expr21 | SOME v => expr22 v Is there a way to resolve the types of rules don't agree error caused by trying to pattern match e11 to p2 , other than enclosing p1 's expression in parenthesis? The p2 pattern has another case statement, to avoid the 'just switch the patterns' answer ;-).

Running Android 2.1, preferences and other dialogs have white/blue text. Looking at theme values I see things like textColorPrimary and textColorSecondary. If I reference those colors in my layout xml, with something like: android:textColor="?android:attr/textColorSecondary" I just see white text (I have tried textColorPrimary, textColorTertiary and textColorHint also). I do not have any theme values stated in my manifest file. I am presuming this means I am using the system default theme. All that said, am I barking up the wrong tree with textColor* references? all the textColor* attributes

#include <stdio.h> #include <cstdlib> rec(); main() { int a, fact; char q, n, y; printf("\nEnter any number "); scanf("%d", & a); fact = rec(a); printf("Factorial value = %d\n", fact); printf("do you want to exit.....(y/n):"); scanf("%s" ,&q); if (q == 'n') { system("cls"); main(); } else return 0; } rec(int x) { int f; if (x == 1) return 1; else f = x * rec(x - 1); return f; } I'm using code blocks but I don't know how to clear the screen. I searched then found system("cls"); within header file #include<cstdlib> , but it shows the error cstdlib: no such file of directory . What should I do ?