I understand why ENUM/SET support is not being fully integrated with
scaffolding/bake.But... the table cache is becoming a joke!
($_tableInfo)
Judging from the developer's comments on the latest trac bug reports
regarding the ENUM support, they are dropping them. But why does the
table cache store ENUM as 'type'=>'enum(0)' and 'length'=>0?!?! It
should AT LEAST list it as 'type'=>"enum('value1','soOn')" or as
'type'=>'enum' and replace length with a parameter that correctly
states the property of that field.. not just length as an integer...
I did modify my local cake to return the correct _tableInfo for ENUM
types, but i think 'mysql database support' by definition should
include at least the correct table info so we'd be able to use the
data to build out forms or whatever...
Abstraction doesn't mean that anyone should assume a table property
should always be 'length' as an integer.. right?I will repeat myself.. I don't expect ENUMs to be fully supported.. I just want the correct table information to be stored in the cache. I also know that i can use cache() and whatnot to store my own data.. but i still think it's a bad idea to not have this as a default 'feature'. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
