Changes between Version 16 and Version 17 of TracTicketsCustomFields

Timestamp:

Nov 16, 2006, 11:46:00 PM (17 years ago)

Author:

Tim Hatch <trac@…>

Comment:

Fixing docs about ticket_custom for #4197

TracTicketsCustomFields

@@ -75 +75 @@
 === Reports Involving Custom Fields ===
 
-Custom ticket fields are stored in the `custom_ticket` table, not in the `ticket` table. So to display the values from custom fields in a report, you will need a join on the 2 tables. Let's use an example with a custom ticket field called `progress`.
+Custom ticket fields are stored in the `ticket_custom` table, not in the `ticket` table. So to display the values from custom fields in a report, you will need a join on the 2 tables. Let's use an example with a custom ticket field called `progress`.
 
 {{{
@@ -81 +81 @@
 SELECT p.value AS __color__,
    id AS ticket, summary, owner, c.value AS progress
-  FROM ticket t, enum p, custom_ticket c
+  FROM ticket t, enum p, ticket_custom c
   WHERE status IN ('assigned') AND t.id = c.ticket AND c.name = 'progress'
 AND p.name = t.priority AND p.type = 'priority'