rake db:test:prepare vs. rake db:test:clone

PostgreSQL 8.1.5 Rails 2.3.2 CentOS 5.3

I have discovered when using postgresql as the test dbms that these two tasks create different schemas. db:test:prepare creates a database with all functions and triggers defined in the development schema while db:test:clone omits these elements and creates only the tables, keys and sequences.

I asked about this on #rubyonrails IRC and got the standard "opinionated software" response. However, it seems given the discrepancy in behaviours that there might be a problem here. Is there a reason why cloning a postgresql database "should" exclude things like functions and triggers?