Modify ↓
#8239 closed defect (duplicate)
TicketNotificationSystem assigns reserved SQL keyword 'new' to ticket attributes.
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | notification | Version: | none |
| Severity: | major | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
In some circumstances this leads to
ProgrammingError: syntax error at or near "new" at character 19
https://trac.edgewall.org/browser/trunk/trac/ticket/notification.py?rev=7890#L136
Does it even use this parameter anywhere?
I believe this occurs when ticket.save_changes is called *after* TicketNotifyEmail.notify. This doesn't happen anywhere within Trac normally but can lead to problems when writing plugins.
Attachments (0)
Change History (6)
comment:2 by , 15 years ago
| Component: | ticket system → notification |
|---|---|
| Milestone: | → 0.11.6 |
| Owner: | set to |
Proposed fix seems OK. Ideally, you could contribute a patch!
comment:3 by , 10 years ago
| Milestone: | next-minor-0.12.x → next-stable-1.0.x |
|---|
comment:4 by , 9 years ago
| Owner: | removed |
|---|
comment:5 by , 8 years ago
| Milestone: | next-stable-1.0.x → next-stable-1.2.x |
|---|
Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.
comment:6 by , 8 years ago
| Description: | modified (diff) |
|---|---|
| Milestone: | next-stable-1.2.x |
| Resolution: | → duplicate |
| Status: | new → closed |
Duplicate of #8620.
Note:
See TracTickets
for help on using tickets.
I'm trying to figure out a fix to this. The simplest method seems to be just copying the entire ticket object before
TicketNotifyEmailstarts modifying it, this seems a bit untidy to me though.