conventions

I have the following tables: - posts - files - events - documents Every post, file, event, document can have comments. What is the better database scheme for this, and why ? First solution comments table (comment_id, author_id, comment) 4 tables to create relations (posts_comments(post_id, comment_id), files_comments(file_id, comment_id), events_comments(event_id, comment_id), documents_comments(document_id, comment_id)) Second solution comments table (comment_id, author_id, comment) items_comments (comment_id, parent_type (enum['post', 'file', 'event', 'document']), parent_id) What is a

I'm trying out pylint to check my source code for conventions. Somehow some variable names are matched with the regex for constants ( const-rgx ) instead of the variable name regex ( variable-rgx ). How to match the variable name with variable-rgx ? Or should I extend const-rgx with my variable-rgx stuff? e.g. C0103: 31: Invalid name "settings" (should match (([A-Z_][A-Z1-9_]*)|(__.*__))$) Somehow some variable names are matched with the regex for constants (const-rgx) instead of the variable name regex (variable-rgx). Are those variables declared on module level? Maybe that's why they are

If I have have some overloaded ostream operators, defined for library local objects, is its okay for them to go to std namespace? If I do not declare them in std namespace, then I must use using ns:: operator << . As a possible follow-up question, are there any operators which should go to standard or global namespace? According to Koenig Lookup (C++ Standard 3.4.2) operator<< will be searched in namespaces of arguments. No need to declare it in std namespace. Herb Sutter operator<<( ..., MyClass ) should go in the same namespace as MyClass . You should think of it as part of the interface of

I'm using class members to hold constants. E.g.: function Foo() { } Foo.CONSTANT1 = 1; Foo.CONSTANT2 = 2; This works fine, except that it seems a bit unorganized, with all the code that is specific to Foo laying around in global scope. So I thought about moving the constant declaration to inside the Foo() declaration, but then wouldn't that code execute everytime Foo is constructed? I'm coming from Java where everything is enclosed in a class body, so I'm thinking JavaScript might have something similar to that or some work around that mimics it. All you're doing in your code is adding a

Is there a tool to run code convention tests in clojure? For example, make sure function names don't have any capital letters or keywords don't have any underscores in them. Two useful Leiningen plugins I learned about recently: lein-bikeshed lein-kibit Venantius Late to the party here. Seconding noahlz , the three main static analysis tools that I use on a regular basis are lein-bikeshed , lein-kibit , and Eastwood , though I also use yagni . Each of these has different strengths. Bikeshed is good for general code cleanup but is mostly focused on style (e.g. making sure lines aren't too long,

Having a background in Java, which is very verbose and strict, I find the ability to mutate Python objects as to give them with fields other than those presented to the constructor really "ugly". Trying to accustom myself to a Pythonic way of thinking, I'm wondering how I should allow my objects to be constructed . My instinct is to have to pass the fields at construction time , such as: def __init__(self, foo, bar, baz=None): self.foo = foo self.bar = bar self.baz = baz But that can become overly verbose and confusing with many fields to pass. To overcome this I assume the best method is to