Ok, back again... creating a new attribute with a longer length
specified seems to work, rather than  trying to modify the
specification of an existing column. Perhaps this reflects the
underlying contraints of mysql?


On Apr 7, 6:48 am, MarkMT <[email protected]> wrote:
> On Apr 7, 6:36 am, MarkMT <[email protected]> wrote:
>
>
>
> > On Mar 18, 3:58 pm, Michael Klishin <[email protected]>
> > wrote:
>
> > > keep in mind that in 0.9.10 (latest released version) default string  
> > > length is 50 characters
> > > that a lot of people (myself included) find retarded
>
> > > in 0.10.0 (next branch) it defaults to 255 characters long, but even  
> > > so it may not be enough for content
> > > field
>
> > > "larger" type is DataMapper::Types::Text, provided by dm-core
>
> > I just ran into this string length issue while trying to figure out
> > why a record I had created was silently failing to save (is this
> > documented someplace? - could have saved me a lot of time if I'd known
> > about the default).
>
> Ok I did just find the documentation - I had been looking at the
> property method documentation, but this detail is in the Property
> class documentation.
>
> Would still appreciate advice on how to fix my problem.
>
>
>
> > I tried adding :length => 128 and autoupgrading, but when I access the
> > table I get a mysql error "Data too long for column 'item_description'
> > at row 1", which sounds like it's having a problem with an existing
> > record whose string attribute has a length well below 50. Can someone
> > suggest what I'm doing wrong here, or what the right way is to adapt
> > my table to accommodate longer string lengths?
>
> > Mark.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"DataMapper" 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/datamapper?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to