Hi Marco, On Mon, Apr 16, 2012 at 18:46, Marco Vannini <marco.vann...@gmail.com> wrote:
> you are right, sorry for the big caos (that I usually do :D). The problem > Marco > was that before 3.1.3 postmaster filter was able to land mail in queue > correctly either if there were some "mistake" (upper vs lower case) and the > same kind of problem I've found on ticket type assignment where in this case > I had a space in the type definition (and not in the filter assignment). > > undoubtedly now it's cleaner but I've been caught by panic :D > > Due to this I don't know if those behavior has to be considered as bug or it > will be a good point to put a note on the upgrade as issue. this is actually very nasty. In OTRS 3.1.3 we created lots of caching; this means fewer database requests which is generally a 'Good Thing (TM)'. If you run OTRS on MySQL or a database with a case insensitive collation (i.e. NOT Oracle) you could always create a ticket in a queue or ticket type regardless of case. Because if you do 'SELECT id FROM queue WHERE name = 'pOSTMASTER' it will give the exact same result as when you do 'SELECT id FROM queue WHERE name = 'Postmaster' In this case, since 3.1.3 we no longer check the database, we check the cache, and also we do not fall back to checking the database if we can't find it. And the cache is always case sensitive. I'm not quite sure if I consider this a bug but it certainly is a change in behavior! -- Mike. --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
