[REQ] Improve setup of fields of type ENUM/SET

Shooter7119 / sequel-pro

Automatically exported from code.google.com/p/sequel-pro

Other

0 stars 0 forks source link

[REQ] Improve setup of fields of type ENUM/SET #160

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Try to create an ENUM/SET field.
2. Deviate from the rigid syntax - non-quoted/non-comma-separated Length, or 
quoted Default - 
and see unhelpful SQL error.

We could provide client-side validation before submitting the request to the 
server and provide 
friendlier help, or we could provide an improved interface when editing ENUMs 
and SETs.

Original issue reported on code.google.com by rowanb@gmail.com on 4 Feb 2009 at 10:56

GoogleCodeExporter commented 9 years ago

Original comment by stuart02 on 5 Mar 2009 at 10:23

Added labels: Priority-Medium

GoogleCodeExporter commented 9 years ago

Original comment by avenja...@gmail.com on 14 May 2009 at 3:41

Changed title: [FIX] Improve setup of fields of type ENUM/SET

GoogleCodeExporter commented 9 years ago

Original comment by stuart02 on 16 Nov 2009 at 2:40

Changed title: [REQ] Improve setup of fields of type ENUM/SET

GoogleCodeExporter commented 9 years ago

Original comment by abhibeck...@gmail.com on 24 Mar 2012 at 1:09

Added labels: Milestone-ReleaseFuture