Adding field to customers table

I'd like to add a simple timestamp column to the end of the customers table. I know how to do it, but just thought I'd check and see if anyone know a reason not to do it. I don't want to break anything that would depend on there being a certain number of columns or something silly like that.

Why?

What's this "timestamp" for?

There's already a last_modified column which is a timestamp indicating the last change.

The field would be for when the record was created (aka when the account was created). In one case, I wanted to use an external newsletter mailing and wanted to pull customers who created accounts and opted-in since the previous mailing. In another case, I just wondered how many accounts were created this month or that month.

So would that break anything?

It's a waste of your time. Why make the database schema more complicated and more to maintain needlessly?

There's already a date-created and last-modified date stored for each customer record: just do a join on customers and customers_info and you'll have all that information.

DrByte:

It's a waste of your time. Why make the database schema more complicated and more to maintain needlessly?

There's already a date-created and last-modified date stored for each customer record: just do a join on customers and customers_info and you'll have all that information.

"That data is already being captured in customers_info" is what I needed to hear. thanx.