Different variable name case convention in one application

Question

This is a really trivial problem. I am just curious on how to deal with this in a "professional" manner.

I am trying to stick to variable naming convention. For NodeJs I am doing camelCasing. For database, I am using PostgreSQL and using underscore_casing.

Now the problem arises when I query data from PostgreSQL. I'll get a user object with following format,

{user_id: 1, account_type : "Admin"}

I can pass this object directly to server side-render and will have to use underscore casing to access account_type. Of course, I can manually create a new user JSON object with property userId and accountType but that is unnecessary work.

Is it possible to follow variable naming convention for both language and avoid having mixed variable names casing in some files? What is a good way to stay organized?

Answer 1

The are two good ways to approach this issue. The simplest one - do no conversion, use the exact database names. And the second one is to camel-case columns automatically.

Either way, you should always follow the underscore notation for all PostgreSQL declarations, as it will give you the option to activate camel-casing in your app at a later time, if it becomes necessary. Never use camel-case inside the database, or you will end up in a lot of pain later.

If you want the best of both worlds, follow the underscore notation for all PostgreSQL declarations, and convert to camel-case as you read data.

Below is an example of how to do it properly with pg-promise, copied from event receive example:

// Example below shows the fastest way to camelize column names:

const options = {
    receive(e) {
        camelizeColumns(e.data);
    }
};

function camelizeColumns(data) {
    const template = data[0];
    for (var prop in template) {
        const camel = pgp.utils.camelize(prop);
        if (!(camel in template)) {
            for (var i = 0; i < data.length; i++) {
                const d = data[i];
                d[camel] = d[prop];
                delete d[prop];
            }
        }
    }
}

Also see the following article: Pg-promise and case sensitivity in column names.

UPDATE

The code above has been updated for use of pg-promise v11 or later.