Well what I HAD meant was that on GAE wherever I'd supplied a newline char as
input I'd see an odd encoding in the storage file. When I queried the database
I didn't see the newline in the response. Now I realize how silly I was. When I
run the same code against sqlite I see the literal newline chars and that
created an errant presumption. My apologies for the false alarm.
On Apr 27, 2010, at 1:18 AM, mdipierro wrote:
> What do you mean exactly "you get no new line"?
>
> 1) you cannot insert strings containing new lines
> 2) the new lines disapper when you extract the data (get replaced by
> something else?)
> 3) you do not see the newline when you display the field values (are
> you sure this is not an escaping issue '\n' vs '<br/>'?)
>
> does it behave differently on GAE vs non-GAE?
>
> Massimo
>
> On Apr 26, 11:35 pm, "G. Clifford Williams" <g...@notadiscussion.com>
> wrote:
>> Had:
>> Field('content', 'text', length=1500, requires=IS_NOT_EMPTY(),
>> label='Gripe'),
>> and then tried:
>> Field('content', length=1500, requires=IS_NOT_EMPTY(),
>> label='Gripe', type='text'),
>>
>> in both cases I get no 'new line' characters.
>>
>> (running 1.76.5)
>>
>> On Apr 23, 2010, at 9:20 PM, mdipierro wrote:
>>
>>> Should be the default behavior? Probably yes.
>>
>>> Meanwhile you can use Field(type='text')
>>
>>> On Apr 23, 8:24 pm, "G. Clifford Williams" <g...@notadiscussion.com>
>>> wrote:
>>>> according
>>>> tohttp://code.google.com/appengine/docs/python/gettingstarted/usingdata...need
>>>> to use multiline=True to get strings to behave with newline chars on GAE.
>>>> Is there a prescribed mechanism by which we accomplish this in web2py?
>>
>>>> --
>>>> Subscription settings:http://groups.google.com/group/web2py/subscribe?hl=en
