An inner join? The help guide says to use an left outer join which is what I attempted (and it failed) - if its supposed to be an inner join the guide should really be changed.
On 3/2/07, Noah Kantrowitz <[EMAIL PROTECTED]> wrote: > > > On Mar 2, 2007, at 7:15 PM, [EMAIL PROTECTED] wrote: > > I dug around in the db file using sqlite3.exe and discovered that a > > new field for my custom ticket field had NOT actually been added into > > the custom-ticket table. Instead the name of new field had just been > > inserted into the default "name" field and when a map was chosen it > > was inserted into the default "value" field. I tried to discover if > > this had happened to anyone else, but could not find an instance of > > it. > > > > Does anyone know why this would have happened and how to fix it? > > Thats the way it is supposed to work. That table contains all custom > fields. If you added a second custom field you would see two entries > for each ticket (with the name of each field in the "name" column). > You will need to do an inner join to get the data you need. > > --Noah > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
