Reading back through I might still not have explained simply enough.

I have a VehicleSearch Model with a m2m to Vehicle and a FK to User. I
want to be able to notify the user that has the VehicleSearch object
when a vehicle inside of the m2m has been added or updated.

I'm looking for the best way to cross reference the new ones and the
best way to handle the notifications that the specific VehicleSearch
was updated with N new vehicles and there were changes to N vehicles.

TIA

On Apr 23, 10:42 pm, Timboy <corn13r...@gmail.com> wrote:
> Let me be more specific to my needs:
>
> Here is my example AutoSearch model:
> name = charfield
> uuid = uuid
> query = charfield
> autos = m2m
> updated = boolean
> emailed_on_update = boolean
> emailed_on_new = boolean
>
> Here are my needs:
>  * updates to this search send the user an email
>  * the user needs to know which autos were updated
>  * new autos email the user
>  * the user needs to know which autos are new
>
> Questions assuming 1000 users.
>
>  * Should this be a cron?
>  * should I add two more m2m's to autos 1 for new autos and 1 for
> updated autos? or is there a better way to keep track for the user?
>
> Thanks.
>
> On Apr 23, 10:20 pm, Alex Gaynor <alex.gay...@gmail.com> wrote:
>
> > On Fri, Apr 24, 2009 at 1:15 AM, Timboy <corn13r...@gmail.com> wrote:
>
> > > I want my users to be able to be updated for changes to specific
> > > models objects.
>
> > > Let's say a user does a search of vehicle listings and the search
> > > returns 3 cars. I want them to be able to be alerted when any of those
> > > three car listings get updated. What's the best way to accomplish
> > > this?
>
> > > TIA
>
> > The first thing to figure out is will this feature be for any model or for a
> > specific one?  The next step is to set up a DB table, it's probably going to
> > just be a few columns, a foreign key to user(or maybe just an email field if
> > you want unauthenticated users to be able to sign up for updates), and a
> > foreign key to the model(or a generic foriegn key).  Then you'd write a
> > signal handler, probably a post_save one, that sends out an email to the
> > appropriate people if it determines that the object has been changed, and it
> > would just send emails to everyone who's email is in the table.
>
> > Alex
>
> > --
> > "I disapprove of what you say, but I will defend to the death your right to
> > say it." --Voltaire
> > "The people's good is the highest law."--Cicero
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to