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

Define your own database table for the email queue #175

Open
danjirovec opened this issue Apr 11, 2024 · 3 comments
Open

Define your own database table for the email queue #175

danjirovec opened this issue Apr 11, 2024 · 3 comments
Labels

Comments

@danjirovec
Copy link

danjirovec commented Apr 11, 2024

Hello, is there a way to define your own Postgres table for the email queue or do I have to use the one generated but the package?

@spookylukey
Copy link
Contributor

The way that models work in Django is that the framework chooses the table name based on the app name and model name. This package just uses that.

Is there a reason you want to change it?

@danjirovec
Copy link
Author

The way that models work in Django is that the framework chooses the table name based on the app name and model name. This package just uses that.

Is there a reason you want to change it?

Sorry what I meant to say was if I can define my own model. The usage docs mention that after I run migrate command, Message table is created which serves as email queue. My question is if I can point Django mailer to use my own model as email queue.

@spookylukey
Copy link
Contributor

There isn't a way to do that at the moment. What is the particular use case you want to support i.e. it what way is the provided model insufficient for you needs?

@pinax pinax deleted a comment from Coin-Degen Apr 13, 2024
@pinax pinax deleted a comment from Coin-Degen Apr 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants