*** mnemoc_ has joined #gnuenterprise *** mnemoc has quit IRC *** reinhard has joined #gnuenterprise *** chillywilly has quit IRC *** Vee has quit IRC *** chillywilly has joined #gnuenterprise *** Vee has joined #gnuenterprise *** sjc has joined #gnuenterprise *** kilo has joined #gnuenterprise *** jerome has left #gnuenterprise good morning morning kilo hi lekma *** btami has joined #gnuenterprise good morning all just FYI after the release has been sent out yesterday, we are again in early breakage state *** dcmwai has quit IRC hi reinhard the releases are ok on win32 great thanks for testing the sample.gfd problem was the good old comma as decimal separator in my localised XP oh crap, I forgot about that issue completely just i forgot it to fix ho problem it's ok if i change it to point and can't reproduce it on any other XP box :) probably dependent on service pack and whatever else... btw. what are yours plan regarding breakage ? I want to do a major cleanup of gnue.common.datasources johannes is working on a complete rewrite of the class repository both being purely internal changes with no visible changes for the user except that some things might become a little faster (say, factor 10) :) :) *** sjc has quit IRC ok, thx only by 10? scandal... 8-)) *** Vee2d2 has joined #gnuenterprise *** Vee has quit IRC *** btami has quit IRC off to customer l8r all *** reinhard has quit IRC *** kilo has quit IRC *** jcater has joined #gnuenterprise *** jamest has joined #gnuenterprise *** reinhard has joined #gnuenterprise jamest, jcater: any chance you can somewhat follow the things I do and tell me if I break something? my users tell me you use svn? of course! what else would you use? lol and update regularly? no reinhard: whats up? what do I need to follow? doing a little code cleanup in common I'll be following it then already did the first commits if there are methods or properties of an object that start with _ is it safe to assume that they are not used outside gnue? (e.g. in a trigger code of your forms) i'm 99% sure I only use exposed fuctions in triggers so yes ok not so sure about all my common based stuff let me check something I would like to increase encapsulation for example instead of accessing RecordSet._modifiedFlags[fieldname] from the outside go over defined procedures (setField for example) and then, when it's really only used from within RecordSet, rename it to __modifiedFlags to make it really private (if you agree with that plan) i'd like to see that this would, for example, help to sort out those case problems we have throughout datasources yes as you could do that lower() in a single point and it would be safe for everything i look clean in all recent gnue-common derived code so IMHO it'd be great to go for it hupo wow, this window was in backscroll land for like three days *** tiredbones has joined #gnuenterprise *** lekma has quit IRC *** johannesV has joined #gnuenterprise reinhard, you could use utils.CaselessDict to solve the case-problem ... i can commit it if you like there it is .... *** sjc has joined #gnuenterprise johannesV: thanks :) johannesV: however, the problem is that some parts of the code consider the dictionary as classeles while others don't s/classles/caseless/ but using the caseless dict it doesn't matter wether one uses a Key or a kEy or a KEY ... *** someon has joined #gnuenterprise Question... if there is going to be a significant rewitre, can an implicit clause be added to the SQL strings? ie. add an extra "where 'userGroup' in (self.user.groups)" Such that self.user is the currently logged in user, and proerty groups is a list of the groups to which the user belongs... 'userGroup' would then be a per-entry field that can control which groups can view the record... as far as I am concerned, there is not going to be a significant rewrite but rather a cleanup of what's here Oops... would need to also have "or 'userGroup' = $NULL$" Fair enough. I'm not planning about *any* new feature actually I have two major problems to contributing to GNUe... (1) no decent home 'net connection and (2) Don't know python. I think that (2) is the bigger problem. but maybe, as a result of this cleanup, implementing new features could become easier as the code would be structured better (2) is something you can fix in an afternoon :) That assumes that I have an afternoon :D *lol* well, the fact that you talk about contributing itself assumes that you have an afternoon :) I lurk the logs on a regular basis, and have been asked by superiors at work if GNUe could be used... It's lacking two things that the incumbant program has... row-level security and column level security. I would say that the implicit clause to the SQL string would take care of the first, but I'm not sure how to implement the second (column-level security) well, the fact that you talk about contributing itself assumes that you have an afternoon :) Point taken. I'm not sure if matricies can be used efficiently in Python with SQL. I don't see why it couldn't though. ie if (1 2 3 4 5) in (2 8 10) then... would be true... (1 == 2) or (2 ==2) or (3==2)... OK... gotta run... I'll keep an eye to the logs to see how badly the ideas get flamed :) *** someon has quit IRC jamest, jcater: strategy question some objects in the dbdriver system (e.g. Connection) have methods that are called externally and implemented differently by the different drivers e.g. Connection.close currently, they are defined in the Base driver with pass, and overwritten by the drivers now times are a-changing and there are (to stay with this example) things that should *always* be done on close (e.g. cleaning up references to let the garbage collection do it's work) there's on point in the Base driver where such code could be put I'd propose to generally (as a rule) do a close and a _close in such cases where the close in the start just calls _close and _close is a placeholder to be overwritten by drivers but if things have to be added in the base driver, it can be done in that close method much like it's done for createResultset and _createResultset what would you think? wow, latest stats from repository-rewrite: time to load repo before rewrite (with debug-level:0-8) 16.334 seconds, after rewirte (same debug-levels): 1.320 seconds appserver seems to work well with new repository, but i'll do further testing tomorrow ... johannesV: excellent! great work would also be interesting how performance changed for "normal operation" of appserver (load, store, request, fetch) ok, i'm off for today ... *** johannesV has quit IRC reinhard: makes sense to me ok *** SachaS has joined #gnuenterprise *** SachaS_ has joined #gnuenterprise *** kilo has joined #gnuenterprise jamest, jcater: can anybody please check why epydoc docs haven't been generated any more since november last year? i'll look in a bit thanks *** SachaS has quit IRC *** ajmitch has quit IRC *** ajmitch has joined #gnuenterprise *** tiredbones has quit IRC reinhard: epydoc is running i've been looking into it between tasks but it's not giving any errors so I imagine it's being built in the wrong place thanks oh i may have to try and fix this when I get home it's expected to be in http://www.gnuenterprise.org/tools/common/docs/api/ night that url claims to have been created today *** SachaS_ has quit IRC at about the time I did my 1st test run yeah, it *is* current now so probably it simply doesn't get started automatically? i just hand ran the cronjob script which would imply some sort of environment setup that a login shell has vs a shell created by cron *** kilo has quit IRC *** jamest has left #gnuenterprise night all *** reinhard has quit IRC *** jamest has joined #gnuenterprise *** sjc has quit IRC *** deci has joined #gnuenterprise *** dcmwai has joined #gnuenterprise *** deci has quit IRC *** newbie has joined #gnuenterprise hi hi *** newbie has quit IRC *** deci has joined #gnuenterprise *** deci has quit IRC *** deci has joined #gnuenterprise *** deci has left #gnuenterprise *** holycow has joined #gnuenterprise