[REQ] Infer column type from column name for new columns

[GoogleCodeExporter]

I've been using Sequel Pro for a long time, and one repetitive task I find 
myself doing quite often is setting the column time for a column named 
'timestamp.'

What I am proposing is having the column get automatically set to 'TIMESTAMP' 
when you create a column named 'timestamp.'  I've, personally, never come 
across a situation where a column I named 'timestamp' required a different 
datatype. 

This would save some time for people like me who create tables in batches, and 
have applications that use timestamps heavily. 

Thanks for your time,

David

Original issue reported on code.google.com by da...@delcoe.com on 9 Aug 2012 at 3:17

[GoogleCodeExporter]

Well "timestamp" could also mean a UNIX timestamp which would be an INT.

But indeed it would be no harm if we would guess some datatypes from column 
names for new columns.

What conventions are there though?

Original comment by schlabbe...@gmail.com on 9 Aug 2012 at 9:02

• Changed title: [REQ] Infer column type from column name for new columns
• Changed state: Accepted
• Added labels: Priority-Low

[GoogleCodeExporter]

Well, you could potentially do it for all of the various date/time-related 
datatypes. DATE, DATETIME, and TIMESTAMP. 

I'm trying to think of any other sure-fire datatype predictions. Columns named 
'name' or 'username' or 'email almost always go to VARCHAR or TINYTEXT. 

What else?

Original comment by da...@delcoe.com on 9 Aug 2012 at 9:25