Hi, *@Matthew: *I've just tried with a blank database, and everything appeared to work perfectly. I couldn't reproduce the bug I'm seeing now. The database structure looks identical though; in both cases the table name is "finance_transaction", not "main.finance_transactions".
*@Michal: *I'm pretty sure the settings.py is ok, but here it is just in case. I wouldn't be here if I didn't think there was something wrong :) https://pastebin.com/yKzAjBcX (p.s.: Yes my secret is safe) Thank you for your help, Matthew's suggestion gave me a possible solution (i.e. manually transfer my data to a new database), but I would like to avoid that if possible. Michel Lavoie [email protected] On Mon, Oct 8, 2018 at 11:22 AM Michal Petrucha < [email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On Mon, Oct 08, 2018 at 10:29:30AM -0400, Michel Lavoie wrote: > > Hi Matthew, > > > > Thank you for the suggestion, but as I mentioned the error is not limited > > to my views.py; it's also present in the auto generated admin page. > > Basically in the example I gave, I call the delete() method from my > > transaction object, by id. > > > > There's also the "main."prefix in the error that bothers me, in addition > to > > the "s" at the end of the table name. But I'm sure that it doesn't come > > from my views.py, this error appeared after upgrading to 2.1. My app's > code > > is on GitHub: https://github.com/miek770/huitcent/tree/master/finance > > > > Thanks, > > > > Michel > > Hi Michel, > > I also took a glance, and didn't find anything suspicious. Is there a > chance that you have multiple databases defined in your settings, and > a router that directs write queries for the Transaction model to the > wrong one? > > Michal > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iQIcBAEBCgAGBQJbu3YYAAoJEHA7T/IPM/klrZ8P/1FAI/sm5UEMOUSnxjLM6fI+ > /9Lu7/7ZhFvKFVXOSa6GT2pxEjOkdLmtmMwQv1ghvxgvCmVMEohOKoNDPDwhdEGA > VvYuBD7rNhmBqPTwGYdn2ci4fFIK3EaaMuv5pBkdW/ztWcyFgZaJFA1T8KEYR+nR > /8ZBcZOhcZAGpdqppCIZoJTPsHcRggAt2CGWvNzFC9BxFh3w+BqTfTkBLfa2ZQpg > MmBEpqu5VGsOIG3nlULnvnzBMhJEy8IkGf8TTmp0MUeRUycnRQnsCfIVjqDfQuGo > aetk6Jdb9C9760STJnPp7FAdtQqIYj8vdy0NU2KoM9hhxZk80YOuC1PCqDkteuRH > SmkwH5kI5FZKiKAeDUPBn4h2hvkMm/5B1kqtk+BzzAZPCY5CRkmJno+BjCWb0nFE > zSOA/i01a4hlEbhBNDjeYyxvuVVigGGXYBfLuuagIGz/61axu/pWn18sGElRqr+r > 0T0c63QxuOtj6ZCJ5HrtMDRfzfnAjrRImqxmviQJo10XRKSsLavRYqIuKC1AgKFq > K+2c6cel4wb+n698FEAK24ic7gYR+ZH5kX0qOEXUMB2ND5DMKBKaqdkr7S3EqgIm > 7KiuM/oL8SCxAdKKzJvvZyLwSgoDQxcAWng6YccWIZk5C5gcJHwI0wljjfPP0U3v > pUFCfu/sRN9umoHyryiF > =8Eai > -----END PGP SIGNATURE----- > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/20181008152200.GD18928%40koniiiik.org > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAK%3D8-RG3qHad5rcWTZ0kvduyypcFyWfM67%3D8V7JA2FJ3OOyVRQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
