Skip to content
This repository has been archived by the owner on Jul 16, 2023. It is now read-only.

Implement Ardent as a trait as well as a Model, so MongoDB can be used as well #276

Open
igorsantos07 opened this issue Nov 1, 2015 · 0 comments

Comments

@igorsantos07
Copy link
Member

It makes little sense to have Ardent as an optional improvement (as a trait), given it would poses confusion to developers if a model has Ardent improvements, and another one don't.

However, if you're not using a relational database, you're probably not extending Eloquent directly - you're using an extension that implements, say, NoSQL. Thus, Ardent cannot be extended at the same time. In these cases, Ardent makes sense being used as a Trait.

This would help users of Mongo + Ardent, that currently needs to reimplement some stuff: ardent-mongodb by @bmcmurray and laravel-mongo-ardent by @Fuitad, for instance.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant