Re: schema_info


#1

your database to another machine, you have to remember to copy that
little information file, too, which is easy to forget. Same with
backups. If the schema info is packaged with the DB itself, backups
and so forth will always preserve the current schema version,
automatically.

Well then what about making the table more useful? For instance a
timestamp
field would help track when the schema was changed, or a log of the sql
executed… Just some thoughts.
.adam


#2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Nov 8, 2005, at 2:05 PM, Adam S. wrote:

Well then what about making the table more useful? For instance a
timestamp field would help track when the schema was changed, or a
log of the sql executed… Just some thoughts.

Or using an AR model with some duck-typing expectations:
config.active_record.migrations.schema_info_class = MyClass

jeremy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)

iD8DBQFDcSvbAQHALep9HFYRAsZGAJ4iB566ETg8qQBPzBcxJolF7crY8QCgrNQj
0sSwH1HnnEAl4KW/hGywO0A=
=Blmb
-----END PGP SIGNATURE-----