Hi,
yes still open. Attached what you requested, hopefully.
Kenneth
def data():
new = 0
serials = db(db.asset_serial.asset_id == request.args(2)).select()
crud.settings.create_onaccept = insert_serial
crud.settings.create_next =
URL('index',vars=session.http_get_vars,args=sess
Is this still an open issue? If so can you post your model and the complete
action?
On Sunday, 9 December 2012 17:02:13 UTC-6, Kenneth wrote:
>
> Hi,
>
> I "converted" the problematic row ( row = db(db.assets.asset_id ==
> form.vars.id).update(asset_name = form.request_vars.asset_name_2) ) into
Hi,
I "converted" the problematic row ( row = db(db.assets.asset_id ==
form.vars.id).update(asset_name = form.request_vars.asset_name_2) ) into
normal SQL and used it on the database directly, works fine.
I made a static version of the same row ( row = db(db.assets.asset_id ==
273).update(ass
The error you are getting is a database error, not a web2py error, it says
you are trying to insert a record with a duplicate id. Perhaps the data is
already corrupted in db.
On Friday, 7 December 2012 00:06:43 UTC-6, Kenneth wrote:
>
> Hi,
>
> this is a legacy table and asset_id is the id for t
Hi,
this is a legacy table and asset_id is the id for the table. So it needs to
be unique. The migration is false, web2py is not able to change the
structure at all.
I'm only trying to update the asset_name not create an new that looks the
same.
Kenneth
Den fredagen den 7:e december 2012
I suspect your asset_id is declared as unique (or was declared as unique,
then you made a migration but db still thinks it is unique).
On Thursday, 6 December 2012 17:37:10 UTC-6, Kenneth wrote:
>
> Hello,
>
> I have a form created by CRUD with some extra fields. assets_label field
> is a dropdo
6 matches
Mail list logo
