11 Commits (b865a629cbbc982b90e6a4650a093a076002a07f)

Author	SHA1	Message	Date
Jens Ulferts	bcd048f7a0	specify rails version on migrations	8 years ago
Alex Coles	36d0f638ba	Fix syntax (w/Rubocop) in db migrations, seeds ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Alex Coles	e0191e759c	Update year in copyright header to 2015 ... [ci skip]	10 years ago
Alex Coles	5158e698bf	Fix syntax (w/Rubocop) in db migrations, seeds ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Alex Coles	a747820eee	Use 1.9+ Hash syntax in db seeds, migrations ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Alex Coles	be6563f6ec	Fix whitespace in migrations ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	11 years ago
Johannes Wollert	8b096975fe	updates copyright headers ... updates more copyright more copyright headers	11 years ago
Philipp Tessenow	444546e2e8	use \A and \z instead of ^ and $ in ruby regexes	11 years ago
Philipp Tessenow	a1e67dd460	new copyright header #1903	11 years ago
Martin Czuchra	c3902e15d4	Adds proper limits on wiki content fields. ... The limits do not apply to postgres, which is why the schema.rb never included them. MySQL would have produced a different schema.rb. Subsequent migrations would break when the limit was not established in MySQL, leading to a much shorter limit. Yes, that is true, no limit results in a field of shorter size than the maximum size for fields in MySQL. Hooray for smart defaults!	11 years ago
Martin Czuchra	d75574adc1	Removes migrations in favor of their aggregation. ... Removes migrations that are included in ChiliProject 2.4.0 and replaces them by a new, aggregated migrations migration. This migration checks for all the previous ones and continues w/ either of the following: (1) No migrations that this migration aggregates have already been applied. In this case, run the aggregated migration. (2) All migrations that this migration aggregates have already been applied. In this case, remove the information about those migrations from the schema_migrations table and we're done. (3) Only a part of the migrations that this migration aggregates have already been applied. In this case, fail miserably.	11 years ago