Issue #2809 has been updated by Luke Kanies.
Seems like the right fix. But on the question of both not failing when the cache fails, but also propagating the error... How would we do that? Somehow collect all non-fatal failures that happened during compilation and add them to the catalog? It's a great idea, but seems pretty darn complicated. ---------------------------------------- Bug #2809: storeconfigs: with mysql impossible to have resource title differing in case http://projects.reductivelabs.com/issues/2809 Author: Brice Figureau Status: Accepted Priority: Low Assigned to: Category: Rails Target version: 0.25.2 Affected version: 0.25.1 Keywords: Branch: With the following resource: <pre> file { "/etc/sv/m44-test/env/MEMOIR44_HOME": content => "content"; "/etc/sv/m44-test/env/memoir44_HOME": ensure => absent; } </pre> I get: <pre> Mysql::Error: Duplicate entry '/etc/sv/m44-test/env/MEMOIR44_HOME-File-116' for key 2: INSERT INTO `resources` (`exported`, `title`, `line`, `updated_at`, `restype`, `source_file_id`, `host_id`) VALUES(0, '/etc/sv/m44-test/env/MEMOIR44_HOME', 103, '2009-11-12 17:00:08', 'File', 85, 116) </pre> The problem is that a VARCHAR field in MySQL does a lookup in a case-insensitive way, so both titles are the same for the MySQL server. I think the correct fix would be to use a BINARY VARCHAR in the schema. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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/puppet-bugs?hl=en.
