Welcome to the Lounge

// sets the integer channel values by name
template<typename Name>
constexpr inline void channel(typename channel_by_index<channel_index_by_name<Name>::value>::int_type value) {
    constexpr const int index = channel_index_by_name<Name>::value;
    channel<index>(value);
}
        
// sets the integer channel values by name
template<typename Name, typename... Names>
constexpr inline void channel(typename channel_by_index<type::channel_index_by_name<Name>::value>::int_type value,
                                typename type::channel_by_index<channel_index_by_name<Names>::value>::int_type... values) {
    constexpr const int index = type::channel_index_by_name<Name>::value;
    channel<index1>(value);
    channel<Names...>(values...);
}

Sander Rossel wrote:

they are spaces

pkfox wrote:

official England are crap at football

swampwiz wrote:

But they have the best lager louts.

• Do not normalize past level 3 for most things. It's not worth the performance hit.
• Do not use old school Hungarian notation like tblUsers for names.
• Learn what an index is and how to properly use it (hint, they help with reads).
• Learn when to use a flattened/denormalized table (hint, when speed is a must or for a reporting db/table).
• If you're in MySQL, learn the different storage types.
• Learn how to use diagrams well.
• For all things pure, make sure you get a proper handle foreign key constraints to help with data integrity.
• Learn when or when not to use a compound key (hint, many to many).
• Speaking of, learn when to use a many to many relationship (hint, clickety).
• Learn the pros and cons of building a self-referential table (hint, when building a hierarchy of data).
• Lean when to use views (hint, permissions and data access restrictions, read only denormalization).
• Understand why concepts like code-first DB design is only purported by those who don't understand proper DB design.
• Understand that by their design relational DBs are slower than non-relational ones.
• Learn to use triggers to automate some things that would otherwise be tedious.
• And for all things pure again, get a grasp on transactions and connection pools.
• Learn to use SQL profiling tools, these will be your BFF.

• Learn when to use one. If you need to do semi-realtime anything, NoSQL is awesome. So, stuff like logging is perfect for it.
• They make a great reporting DB if you want to use this rather than a flattened table in your relational DB above.
• They don't use schemas (for the most part) so the learning curve is a breeze compared to SQL.
• Do not use them for mission critical data where it's ok to run a bit slower when data integrity is paramount.