Skip to content

Conversation

dbwhddn10
Copy link

i think this is better and flexible guideline when assuming switch database (ex:mysql) to mongoDB

i think this is better and flexible guideline when assuming switch database (ex:mysql) to mongoDB
@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling d6a16c1 on dbwhddn10:patch-1 into d9f2c51 on jenssegers:master.

@ghost
Copy link

ghost commented Sep 15, 2014

This will likely cause confusion when someone adds another 'Eloquent' alias and the framework complains. The developer should be aware by looking at the code that the ORM has been modified.

@jenssegers
Copy link
Contributor

The alias in the readme completely optional and up to the developer. The Moloquent alias was actually added by the community. If you want to rename it to 'Eloquent', you are free to do so :)

@jenssegers jenssegers closed this Sep 16, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants