On Tuesday, May 6, 2014 9:36:54 AM UTC-4, Richard wrote:
>
> Hey Anthony,
>
> I listen your presentation yesterday, it was really nice. Thanks for all
> the tricks!
>
> :)
>
> Richard
>
> Thank you. Glad it was helpful.
Anthony
--
Resources:
- http://web2py.com
- http://web2py.com/book (Docume
Hey Anthony,
I listen your presentation yesterday, it was really nice. Thanks for all
the tricks!
:)
Richard
On Mon, May 5, 2014 at 4:36 PM, Anthony wrote:
> Internally, when you store a list of items in a list:string field, web2py
> converts the list to a single string, with list items sepa
Yes Derek that the way to go!
I have a different implementation with multiple form and kind of in row
create/update and no ajax, it is fully web2py form principle...
Richard
On Mon, May 5, 2014 at 5:17 PM, Derek wrote:
> This may be too late, but in any case, you may want to take a look at my
This may be too late, but in any case, you may want to take a look at my
web2pyslice here:
http://www.web2pyslices.com/slice/show/1612/ajax-adding-child-records-to-parent
It's about adding addresses to person records, using ajax.
On Monday, May 5, 2014 1:17:02 PM UTC-7, LoveWeb2py wrote:
>
> D
Solved it!! Thank you so much everyone!
UPDATE YourTable SET YourColumn = CONCAT('|', YourColumn, '|');
Here is the SQL query if you're using MYSQL:
On Monday, May 5, 2014 4:36:56 PM UTC-4, Anthony wrote:
>
> Internally, when you store a list of items in a list:string field, web2py
> conver
Internally, when you store a list of items in a list:string field, web2py
converts the list to a single string, with list items separated by the "|"
character. If you convert to a list:string field, you will need to modify
all of the existing records by wrapping them in "|" characters. So, for
No problem, Richard. Really appreciate all of the help from you and the
rest of the community!
On Monday, May 5, 2014 4:25:03 PM UTC-4, Richard wrote:
>
> I understand what you may need, but you seems to think that things work
> differently that they actually do...
>
> Sorry, I have to go now. M
Why are you doing this? Are you just trying to change the widget that is
used to display and edit?
On Monday, May 5, 2014 1:05:38 PM UTC-7, LoveWeb2py wrote:
>
>
> Rebooted and the address shows up in one field now (not spread across 10),
> but it is still truncated. If I switch the field back t
I understand what you may need, but you seems to think that things work
differently that they actually do...
Sorry, I have to go now. May help again later.
Richard
On Mon, May 5, 2014 at 4:22 PM, LoveWeb2py wrote:
> Richard,
>
> This is actually for editing fields that are already in the SQLF
Richard,
This is actually for editing fields that are already in the SQLFORM.grid()
I checked my error log and I'm getting
Warning: Truncated incorrect DOUBLE value: 'T'
ret = self.cursor.execute(*a, **b)
Could this be causing it?
On Monday, May 5, 2014 4:17:47 PM UTC-4, LoveWeb2py wrote:
>
>
You need a relation for this!!
one table clients and a list:reference field call address_id and another
table call address...
Then you will need to create a custome form that let you add new address
for a given client with a component maybe...
Richard
On Mon, May 5, 2014 at 4:17 PM, LoveWeb2py
and by dropdown I mean clicking the + field that you get when you use the
+- list:string field type
On Monday, May 5, 2014 4:17:02 PM UTC-4, LoveWeb2py wrote:
>
> Derek,
>
> I want to be able to add multiple addresses for one customer using the
> dropdown instead of having to create another new
Derek,
I want to be able to add multiple addresses for one customer using the
dropdown instead of having to create another new record.
On Monday, May 5, 2014 4:15:00 PM UTC-4, Derek wrote:
>
> Why are you doing this? Are you just trying to change the widget that is
> used to display and edit?
>
list:string field type is not for displaying record in list format. There
is SQLFORM.grid() for this or you can start with crud.select() it mays be
easier..
Richard
On Mon, May 5, 2014 at 4:05 PM, LoveWeb2py wrote:
>
> Rebooted and the address shows up in one field now (not spread across 10),
Rebooted and the address shows up in one field now (not spread across 10),
but it is still truncated. If I switch the field back to string and reboot
the ip address appears fine... I really need it in a list form if possible,
but if I can't i'll deal with a string
--
Resources:
- http://web2p
yes... going to try and reboot the whole computer in case I missed a
process. I am running on httpd with wsgi I normally just restart httpd and
it works okay, but we'll see what happens after a full reboot.
On Monday, May 5, 2014 3:57:14 PM UTC-4, Richard wrote:
>
> Did you restart your termina
Did you restart your terminal instance of web2py after change the type of
your field?
Models get load only when you start the session I think...
Richard
On Mon, May 5, 2014 at 3:51 PM, LoveWeb2py wrote:
> When I connect to my table through python web2py.py -S myapp -M
>
> and type:
>
>
> user
When I connect to my table through python web2py.py -S myapp -M
and type:
users_list = db(db.users_id!=None).select()
for row in users:
print row.address
it shows truncated addresses in a list the first and last character are
missing.
When I click on the record in the grid, it shows the reco
You have typo below :
db.define_table('users',
Field('address', *'*list:string')
It truncate the end?
How do you determine it is truncate? In the grid? If in grid() try to set
greater then 20 to maxtextlength parameters of the grid...
Richard
On Mon, May 5, 2014 at 3:34 PM, Love
Richard,
My db.define_table('users',
Field('address',list:string')
use to be Field('address','string')
Soon as I changed it to list:string it truncated all of the addresses in
the DAL. When I iterate through the database
users_list = db(db.users_id!=None).select()
for row in user
Are you talking about field type or representation or requires that all
differents?
Without code can't help...
Sorry.
Richard
On Mon, May 5, 2014 at 2:21 PM, LoveWeb2py wrote:
> I am using MYSQL. So it actually didn't affect the database itself. What
> it did was just change the way the data
I am using MYSQL. So it actually didn't affect the database itself. What it
did was just change the way the data is represented in SQLFORM. Very
interesting. How could I properly represent it?
On Monday, May 5, 2014 2:11:28 PM UTC-4, Richard wrote:
>
> If you didn't backup db before makee your c
If you didn't backup db before makee your change I guess no...
Rollback as notting to do there, it is a migration matter and the way
web2py handle this process...
If were create a new field, the old field would stay there, because web2py
migration don't delete field, but since you change field ty
I had a list of addresses I was using on my user db and when I switched the
field from string to string.list it truncated all of my values. I have over
1000 customers in there.
Is there an explanation for this? It cut off the first and last character
for example: 123 field road is now 23 field
24 matches
Mail list logo
