[ https://issues.apache.org/jira/browse/SYNCOPE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747373#comment-13747373 ]
Hudson commented on SYNCOPE-409: -------------------------------- SUCCESS: Integrated in Syncope-1_1_X #101 (See [https://builds.apache.org/job/Syncope-1_1_X/101/]) Upgrading to Wicket 6.10.0 and adjusting Selenium tests for SYNCOPE-409 (ilgrosso: rev 1516377) * /syncope/branches/1_1_X/console/src/test/java/org/apache/syncope/console/ConfigurationTestITCase.java * /syncope/branches/1_1_X/pom.xml > Allow notifications with empty about field > ------------------------------------------ > > Key: SYNCOPE-409 > URL: https://issues.apache.org/jira/browse/SYNCOPE-409 > Project: Syncope > Issue Type: Improvement > Components: console, core > Affects Versions: 1.1.3 > Reporter: Guido Wimmel > Assignee: Francesco Chicchiriccò > Priority: Minor > Fix For: 1.1.4, 1.2.0 > > Attachments: syncopeNotificationsEmptyAbout.patch, > syncopeNotificationsEmptyAbout.patch > > > Currently, when one creates a new notification in Syncope, one is forced to > enter a user search condition in the "About" tab that allows to restrict the > notifications to specific users. IMO this is not always necessary - it should > also be possible to leave the field empty such that the notification is sent > for all users. > Allowing the Notification.about field to be empty would also improve > performance in this case, as an unnecessary search query to the database can > be avoided. This is especially relevant for MySQL, as we observed full table > scan behaviour for queries executed by AttributableSearchDAOImpl.matches() > (called by NotificationManager) for even very simple search conditions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira