Hi,
On Mon, Aug 24, 2015 at 11:31 PM, Akshita Jha <
zenith158@gmail.com> wrote:
> >
> > Checking might not harm to create a proper error message since it can
> > happen again in the future.
> >
>
> I have sent a patch which checks for "IntegrityError" while inserting packages in table blends_prospectivepackages. Can you please test and confirm ?
Also, nothing is inserted in the table blends_prospectivepackages if this error is raised. I am not sure if this is the best thing to do. Another option could be to ignore the duplicated package (implying the package which comes second) and keep inserting other packages in the table. But, the problem here can be that the first package we get (the package which is inserted), is older than the one that is ignored. What do you think is a better implementation ?