constraints

I'm trying to make it so that I can have a urls like this: /events /events/sunday # => The day is optional However, it doesn't seem to be working even though I know it is getting called. It is at the bottom of my routes file. match '/:post(/:day_filter)' => 'posts#index', :as => post_day_filter, :constraints => DayFilter.new class DayFilter def initialize @days = %w[all today tomorrow sunday monday tuesday wednesday thursday friday saturday] end def matches?(request) return @days.include?(request.params[:day_filter]) if request.params[:day_filter] true end end Here is my rake routes output:

I have two label, L1 and L2 of variable and nonidentical length. I want to place these two label using constraints in Xcode. If possible i don't want to manipulate constraints programmatically. guidance will be appreciated. Right image should be the expected output Requirements, Two labels are non identical in width When running leading space of L1 and trailing space of L2 will be equal distance between L1 & L2, horizontal space is fixed, 10 px UIStackView cannot be used How can I do it from Xcode? What you can do is put both the UILabel inside a UIView and then: Add a leading, top and bottom

(NOTE: Split from Shapeless: Trying to restrict HList elements by their type ) Question 2 - Own Constraint using Coproduct What I really wanted to do is to write a new constraint using Coproduct. trait CPConstraint[L <: HList, CP <: Coproduct] extends Serializable object CPConstraint { import shapeless.ops.coproduct.Selector._ def apply[L <: HList, CP <: Coproduct](implicit cpc: CPConstraint[L, CP]): CPConstraint[L, CP] = cpc type <*<[CP <: Coproduct] = { // TODO: just invented a symbol ... what would be an appropriate one? type λ[L <: HList] = CPConstraint[L, CP] } implicit def hnilCP[HN <:

I'm using a check constraint on a table to restrict what values are inserted in the table.. Here's an explanation of what I'm trying to do If any Product(sedan) is associated to a specific ObjLevel (Toyota) then the same Product cannot be associated to another specific ObjLevel (Lexus) After I apply the check constraint on the table, any insert containing ObjLevel "toyota" or "lexus" fails.. create table ObjLevel( OLID int identity, Name varchar(50) not null ) insert into ObjLevel values('Ford') insert into ObjLevel values('Toyota') insert into ObjLevel values('Lexus') insert into ObjLevel

I have the following table: T(ID primary key, A, B) I want to have pair (A, B) unique but I don't want to have constraint unique(A,B) on them because it will give error on insert. Instead I want MySQL to silently ignore such inserts. I can't use "insert on duplicate keys ignore" because I can't control client's queries. So, can I build such trigger? Or maybe there is some constraint that allows silent ignore? Edit: I dug around and I think I want something like SQLite's "Raise Ignore" statement. Before mysql 5.5. it wasn't possible to stop an insert inside a trigger. There where some ugly work

I have used manually written as well as Grails generated Unit tests for this command object: package myapp @grails.validation.Validateable class SearchCommand { String basisBuild String buildToSearch static constraints = { basisBuild(blank: false) } } After having my hand written unit test fail I used Grails: create-unit-test myapp.SearchCommand I filled in the Unit Test, and made an assertion that should pass per documentation on mocked constraints: package myapp import static org.junit.Assert.* import grails.test.mixin.* import grails.test.mixin.support.* import org.junit.* @TestMixin

I have two tables, with some data loaded in it and the two reference each other. Table B references the primary key of Table A. I manually attempt to delete some table rows from Table A that are present in Table B, and I get this: #1451 - Cannot delete or update a parent row: a foreign key constraint fails ( TableA . TableB , CONSTRAINT TableB_ibfk_2 FOREIGN KEY ( column ) REFERENCES flashcard ( primaryKeyColumn )) I am not quite sure what's up here. From what I understand,if I delete some rows of TableA then they should automatically also delete the corresponding rows present in Table B (i.e