Prefix for table column names

[vishnupeas]

I'm currently working on a project where I have to use prefix indicating the table name along with the column name example, user table will have columns like user_id, user_name or for user_permission table the columns like up_id, up_permission etc.. Like a simple variable like $columnPrefix = "user_" on a Model would make my life so simple. This has to work with all the relations, getters and setters, joins and others.

I have seen disucssions about prefix for table names but not this, so I would like to know why this pattern is not supported in laravel and if its something we can bring to the framework.

[macropay-solutions]

You could override the getAttributeValue function in a base abstract model that extends the Model and do your magic there.
Analog for setAttribute. But that will not work for the query builder.

Or you could use our decorator lib to undecorate the request and decorate the response if the NOT prefixed columns are needed for outside use only, not for internal use. (it is not clear for us if your db columns have the prefix or not)

Basically the decorator allows you to work with mapped columns outside your project and inside you work with the db columns as they are.

There was a lib mappable https://github.com/jarektkaczyk/eloquence-mappable
Maybe that can help you if you need to work internally with them. It should support also eloquent.

[shaedrich]

Why do you want to prefix your columns in your database but not in your codebase?

[macropay-solutions]

I'm currently working on a project where I have to use prefix indicating the table name along with the column name example

This may mean that he has normal columns but he wants to decorate them with prefix in his project. It is not clear if this need is for FE/external usage (case in which our decorator can help him) or for internal usage case in which the mappable unmaintained lib may be of help for him)

[shaedrich]

It was meant as a rhetorical question, hinting at the possibility of introducing unnecessary complexity by wanting to have one's cake and eating it, too rather than either not having prefixes to begin with or—if that's not possible—consistently using the prefix to avoid accidental duplicated prefixes, having to construct dynamic strings from the prefix, etc.

[macropay-solutions]

@shaedrich turns out there is no need for column changes.