Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doctrine Provider #104

Open
talisman-innovations opened this issue Jun 30, 2016 · 2 comments
Open

Doctrine Provider #104

talisman-innovations opened this issue Jun 30, 2016 · 2 comments

Comments

@talisman-innovations
Copy link

Hi

We've developed a custom provider to use the doctrine ORM to store messages. It's been very useful for our project. I've seen some interest in it from others. If I recast it as a new native provider, is it something that you would like to pull into the project? Just want to check before doing the small rewrite required.

Regards

Steven Brookes

@k-k
Copy link
Contributor

k-k commented Jun 30, 2016

@talisman-innovations - Yeah, I'd love to look at what an implementation would look like and if doctrine DBAL makes more sense over the ORM (maybe that was implied?).

I think the only other consideration would be issue #101 - if we were to split the providers out into separate libraries.

@talisman-innovations
Copy link
Author

I've finally got around to submitting this in pull request #110
Let me know what you think.

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

No branches or pull requests

1 participant