IRC logs of #tryton for Friday, 2013-03-15

chat.freenode.net #tryton log beginning Fri Mar 15 00:00:03 CET 2013
2013-03-15 00:45 <cedk> flo0: address has already 2 fields for street
2013-03-15 07:50 -!- mrechte(~mrechte@landtrekker.com) has left #tryton
2013-03-15 08:19 <flo0> cedk: Yes, I know, I decided to build my own address 'module' instead of modifying the existing one. That's not difficult and a good exercise for the start. And you are right, the existing address is using two Char fields.
2013-03-15 08:33 <_snowy_> Hello all. I would like to know if Tryton is planning to participate in GSoC 2013 as a mentoring organisation.
2013-03-15 08:45 <ronaldm> _snowy_: see https://groups.google.com/forum/?hl=en&fromgroups=#!searchin/tryton/gsoc/tryton/YqxpbEZn5ZI/SWif0-PyQZUJ
2013-03-15 08:48 <_snowy_> I see. So does it mean I should wait till March 18 to know if Tryton is really participating or not?
2013-03-15 09:07 <ronaldm> _snowy_ it looks like Tryton is not participating this year
2013-03-15 09:07 <ronaldm> _snowy_ I am digging for an email where someone has shown interest as well
2013-03-15 10:00 <ralf58> Hi all, I have some problems in GUI-programming and data validation. Is there a recommended validation pattern?- In the "on_change_FIELD"-Method I can change data OR raise an error/warning, but not both of them!? - The pre_validate-Method is only called by "write", but not by "create". Is there no common method for data-validation?
2013-03-15 10:02 <cedk> ralf58: your statement is false for pre-validation
2013-03-15 10:02 <cedk> ralf58: you should not raise error on on_change calls
2013-03-15 10:04 <ralf58> cedk: yes, but what is the correct place to raise errors/warnings during dialog?
2013-03-15 10:04 <cedk> ralf58: http://doc.tryton.org/2.6/trytond/doc/ref/models/models.html#trytond.model.ModelStorage._constraints
2013-03-15 10:05 <cedk> ralf58: or the pre-validate
2013-03-15 10:07 <cedk> ralf58: or http://doc.tryton.org/2.6/trytond/doc/ref/models/models.html#trytond.model.Model.pre_validate
2013-03-15 10:07 <cedk> ralf58: pre-validate will be called earlier but it has some limitation
2013-03-15 10:08 <ralf58> cedk: Seems that _constraints are what I looked for! I'll try. pre-validate is only called in write-operations, but not in create-operations. Then you have to code it twice.(?)
2013-03-15 10:10 -!- _snowy_(daf80caa@gateway/web/freenode/ip.218.248.12.170) has left #tryton
2013-03-15 10:31 <cedk> ralf58: that's false, pre_validate is called on write and create because it is part of the _constraint
2013-03-15 12:52 <pobsteta> Would it not be desirable to have a Tryton stand at RMLL ?
2013-03-15 12:52 <cedk> pobsteta: I was thinking about submitting a talk
2013-03-15 14:44 <sisalp> cedk: I plan to attend RMLL if there is something we can do for Tryton
2013-03-15 14:48 <cedk> sisalp: I don't know how RMLL works
2013-03-15 14:48 <cedk> sisalp: I just saw they are looking for talks about business software and freesoftware
2013-03-15 19:35 -!- vcardon(~vcardon@LNeuilly-152-23-15-185.w193-252.abo.wanadoo.fr) has left #tryton
2013-03-15 21:26 <plantian> Is the --profile argument to trytond just for profiling the startup of the server?
2013-03-15 21:29 <cedk> plantian: normally no, but I think it is a not tested feature and most of the time useless
2013-03-15 21:30 <plantian> cedk: Okay, is there a good way to profile running an action keyword in the client? Does it make sense to profile the client or profile the server?
2013-03-15 21:31 <cedk> plantian: when I find something slow, I just look at the SQL queries
2013-03-15 21:31 <plantian> cedk: By inserting print statements? Or it is accessible very tuning the logging filters?
2013-03-15 21:32 <plantian> *by tuning
2013-03-15 21:34 <cedk> plantian: I print the queries in backend/*/database.py: execute
2013-03-15 21:34 <cedk> plantian: but you can tune the SQL server to do that…
2013-03-15 21:36 <plantian> well printing from there is a start, thanks, I will try it
2013-03-15 21:37 <plantian> there are a lot of queries
2013-03-15 21:38 <plantian> ha
2013-03-15 22:26 <plantian> cedk: Does every possible query go through execute() ?
2013-03-15 22:34 <plantian> Is 23 seconds about how long this should take? -- I'm trying to figure this out, it seems to take 23 seconds (although in the client it seems to take 30) to pay the invoice and ship the shipment on a sale in the processing state (this wizard performs that): https://gist.github.com/ianjosephwilson/5173256
2013-03-15 23:37 <cedk> plantian: so it is openning the invoices that took times
2013-03-15 23:38 <plantian> cedk: Well it took 1/3 of the time. It seems that 3702 queries are run in a total of 1.7383215427398558 seconds, so it doesn't seem like the problem is the database. I'm not sure if all the db computation is at the execute method though.
2013-03-15 23:39 <cedk> plantian: there was some improvement in trunk: account changeset 5b61530991e1
2013-03-15 23:40 <cedk> plantian: + the create multi values
2013-03-15 23:43 <plantian> I guess it seems weird to me because the sale has 3 lines and it is around the 10th sale in the database.
2013-03-15 23:49 <cedk> plantian: I'm pretty sure it is changeset 5b61530991e1
2013-03-15 23:51 <plantian> cedk: Do you think that changeset will work in 2.6?
2013-03-15 23:51 <cedk> plantian: it should
2013-03-15 23:51 <plantian> cedk: What about the shipment taking 10 seconds?
2013-03-15 23:53 <cedk> plantian: have you account_stock* modules ?
2013-03-15 23:55 <plantian> cedk: no
2013-03-15 23:58 <cedk> plantian: indeed I don't understand what you try to achieve
2013-03-15 23:58 <cedk> plantian: if you don't care about shipment better to not do it
2013-03-15 23:58 <cedk> plantian: idem for invoice
2013-03-15 23:58 <cedk> ACTION go to sleep

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!