test at 0cfcde309b96bc718db204837a46098c8fcbec60 from tkadom's friendly_id

tkadom / friendly_id

Description:	monkey patched friendly_id that allows for a larger number of duplicate slugs edit
Homepage:	edit
Public Clone URL:	git://github.com/tkadom/friendly_id.git Give this clone URL to anyone. `git clone git://github.com/tkadom/friendly_id.git`
Your Clone URL:	git@github.com:tkadom/friendly_id.git Use this clone URL yourself. `git clone git@github.com:tkadom/friendly_id.git`

friendly id was using the record count to determine the next id for a 
generated slug.  This algorithm does not take into account hat aged 
records might have been removed with the associated rake task.  i.e. if we 
created three slugs from the same base text and had base-val-1, 
base-val-2, and base-val-3 as our slugs initially.  We then run a removal 
of aged slugs, leaving only base-val-2, and base-val-3, we would generate 
a count of 2 slugs which share the same slug root.  the count would then 
try to create a base-val-3 slug which would error out on uniqueness 
validation.  I changed the algorithm so that it is not as efficient, but 
it will actually re-use values that have been deleted by iterating through 
the mathing base slugs until an open slot is found for the new slug.

atlruby (author)

Wed Oct 29 08:24:58 -0700 2008

commit 0cfcde309b96bc718db204837a46098c8fcbec60
tree 7a755ac0f2ab4550baa98605769bc6aab2ca6d84
parent afbb161ac5de41a2079ba53c9555049e37118e7e

friendly_id / test

	name	age	history message
	..
	database.yml		Loading commit data...
	fixtures/
	schema.rb
	sluggable_test.rb
	test_helper.rb
	unique_column_test.rb