The MySQL Set changes are in SVN. Both Rose::DB and Rose::DB::Object were
updated. Please test, or forever hold your peace... :)
-John
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay p
On Nov 16, 2006, at 2:16 AM, James Masters wrote:
> I use ENUM sometimes. It seemed like a straightforward thing to me
> (although I think either MySQL or my interface to it seems to have
> trouble
> with an enum option of the empty string). Leaving aside
> portability, what
> bad design pat
> SET and ENUM in mysql are super dangerous.
> They promote really bad design patterns and lock people
> into MySQL
> specific schema that is a "Complete Fucking Nightmare" to port to
> another DB system. If people did a standard normalized schema, no
> issues would occur when porting
On Nov 15, 2006, at 19:42, Jonathan wrote:
> SET and ENUM in mysql are super dangerous.
> They promote really bad design patterns and lock people into MySQL
> specific schema that is a "Complete Fucking Nightmare" to port to
> another DB system. If people did a standard normalized sc
On Nov 15, 2006, at 19:12, John Siracusa wrote:
[...]
> Ah ha! Hm, seems like an enum crossed with an array. Anyway, next
> question: what about values with commas in them?
"Officially not supported".
> Blah, I just tried it. In typical MySQL fashion, it silently does
> the wrong thing.
On 11/15/06 10:42 PM, Jonathan wrote:
> That said, supporting MySQL is a good thing to do. BUT since rose
> tends to focus people on doing stuff more intelligently, I would
> suggest that the "SET" support require people to set a global
> Rose::DB variable ( $Rose::DB::enable_mysql_set = 1; ) in o
On Nov 15, 2006, at 10:12 PM, John Siracusa wrote:
> Ah ha! Hm, seems like an enum crossed with an array. Anyway, next
> question: what about values with commas in them? Blah, I just
> tried it. In
> typical MySQL fashion, it silently does the wrong thing.
>
> Well whatever, "it's your fune
On 11/15/06 9:55 PM, Ask Bjørn Hansen wrote:
> On Nov 15, 2006, at 18:35, John Siracusa wrote:
>> Does MySQL actually have native SET support?
>
> Yes,
>
> http://dev.mysql.com/doc/refman/5.0/en/set.html
> http://dev.mysql.com/tech-resources/articles/mysql-set-datatype.html
Ah ha! Hm, seems lik
On 11/15/06 10:04 PM, Darren Duncan wrote:
> AFAIK, MySQL has had support for a set-like type
> for a long time; as it has also had support for
> an ENUM type.
I think enums are much older than sets in MySQL. RDBO already has enum
support for MySQL.
-John
-
At 9:35 PM -0500 11/15/06, John Siracusa wrote:
>On 11/15/06 9:12 PM, Ask Bjørn Hansen wrote:
>> Anyway, below is a small addition (without tests) to Rose::DB::MySQL
>> to add support for SET columns.
>
>Does MySQL actually have native SET support? If not, what does this feature
>get you beyond
On Nov 15, 2006, at 18:35, John Siracusa wrote:
> Does MySQL actually have native SET support?
Yes,
http://dev.mysql.com/doc/refman/5.0/en/set.html
http://dev.mysql.com/tech-resources/articles/mysql-set-datatype.html
- ask
--
http://www.askbjoernhansen.com/
On 11/15/06 9:12 PM, Ask Bjørn Hansen wrote:
> Anyway, below is a small addition (without tests) to Rose::DB::MySQL
> to add support for SET columns.
Does MySQL actually have native SET support? If not, what does this feature
get you beyond the Array column type, which is already emulated for MyS
12 matches
Mail list logo
