Thanks Ryan Regarding to the same. What would be easiest way to handle a custom field as a ui-datepicker.
EmeCas On Wed, Dec 13, 2017 at 2:26 AM, RjOllos <rjol...@gmail.com> wrote: > > > On Tuesday, December 12, 2017 at 1:59:01 PM UTC-8, emecas wrote: >> >> Thanks Ryan >> >> Actually, I was wonder if there was a better way to handle it using >> Trac's core. >> >> The problem with the custom field approach, in general, is regarding to >> the additional join it requires that in some cases. Maybe it is not too >> relevant, just from the performance point of view or about queries >> complexity. >> >> Some of my queries sums up 3-6 joins, those with multiple custom fields >> mixed with information from tables related to macros and plugins. >> >> EmeCas >> > > You could write a plugin to add a columns to the ticket table, but it's > generally not advised because you might encounter problems with upgrades in > the future. I think that learning to love the JOINs is your best option. > > - Ryan > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to trac-users+unsubscr...@googlegroups.com. > To post to this group, send email to trac-users@googlegroups.com. > Visit this group at https://groups.google.com/group/trac-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
