search for: ocd

Hello list. I'm thinking to migrate the hole user db from system users to mysql. I already did it in a test environment, but something is annoying my OCD... I don't quote the variables username and password sent to the mysql server. I know, the mysql user that dovecot uses only has select rights, but it stills bother me, because its possible to do an useless sql code injection. Is there a way to quote that? Something like exim's quote_mysql...

...t. Those of you who have used my code will probably realize that I am not a grand architect of R packages =] I'd love to get feedback from those of you with a broader perspective and better software engineering skills than I (a low bar to step over). I have marked a few of these items with an OCD tag since I might be taking it a bit too far. The list: (1) Extend the work of others. There is an amazing amount of unneeded redundancy. There are plenty of times that users implement their own version of a function because there is an missing feature, but a lot of time is spent re-creating dupl...

...argument onto a separate line and > indenting by one tab appears to be the next best solution. Please let me > know if there's if there's a preferred style for cases like this one. Readability has IMO higher priority than some limit of 80 chars. And it hurts readability (at least my OCD) when style changes as you do with indent here. So my personal preference is to fix indent and accect longer lines. But you ask for a preferred style - which I do not think we have in this case. So it boils down to what you prefer. Enough bikeshedding, thanks for the quick response. Sam

...argument onto a separate line and > indenting by one tab appears to be the next best solution. Please let me > know if there's if there's a preferred style for cases like this one. Readability has IMO higher priority than some limit of 80 chars. And it hurts readability (at least my OCD) when style changes as you do with indent here. So my personal preference is to fix indent and accect longer lines. But you ask for a preferred style - which I do not think we have in this case. So it boils down to what you prefer. Enough bikeshedding, thanks for the quick response. Sam

> Am 02.02.2015 um 18:07 schrieb Juan Bernhard: >> Hello list. I'm thinking to migrate the hole user db from system users >> to mysql. I already did it in a test environment, but something is >> annoying my OCD... I don't quote the variables username and password >> sent to the mysql server. I know, the mysql user that dovecot uses only >> has select rights, but it stills bother me, because its possible to do >> an useless sql code injection. >> >> Is there a way to quote...

...verrrryyy nice fade effect going on when you click the navigation for ''new in iPhoto ''08'', ''Organize by Events'' etc. Is it possible to get this effect working with scriptaculous? So far, I''ve managed get things going part of the way with this ocde: "<a href="#" onmousedown="$(''budgetpositionbox'').fade({duration:0.2}); return false;" onmouseup="$ (''researchthemepositionbox'').appear({duration:0.2}); return false;">Research Theme</a>" Where the ''...

...d >>> indenting by one tab appears to be the next best solution. Please let me >>> know if there's if there's a preferred style for cases like this one. >> Readability has IMO higher priority than some limit of 80 chars. >> And it hurts readability (at least my OCD) when style changes >> as you do with indent here. So my personal preference is to fix >> indent and accect longer lines. > > In this case the an often used convention (which is also kind of > readable) is to add a newline after the return values, but before the > functio...

...d >>> indenting by one tab appears to be the next best solution. Please let me >>> know if there's if there's a preferred style for cases like this one. >> Readability has IMO higher priority than some limit of 80 chars. >> And it hurts readability (at least my OCD) when style changes >> as you do with indent here. So my personal preference is to fix >> indent and accect longer lines. > > In this case the an often used convention (which is also kind of > readable) is to add a newline after the return values, but before the > functio...

...X or Unix X11), I get the same result. Thanks to Andy Liaw for helping me tune the code this far. I'm stumped. Would love to hear others' experience with this, and if they can reproduce the problem elsewhere. -- David L. Van Brunt, Ph.D. Outlier Consulting & Development mailto: <ocd@well-wired.com>

...by one tab appears to be the next best solution. Please let me >>>>> know if there's if there's a preferred style for cases like this one. >>>> Readability has IMO higher priority than some limit of 80 chars. >>>> And it hurts readability (at least my OCD) when style changes >>>> as you do with indent here. So my personal preference is to fix >>>> indent and accect longer lines. >>> In this case the an often used convention (which is also kind of >>> readable) is to add a newline after the return values, but...

...by one tab appears to be the next best solution. Please let me >>>>> know if there's if there's a preferred style for cases like this one. >>>> Readability has IMO higher priority than some limit of 80 chars. >>>> And it hurts readability (at least my OCD) when style changes >>>> as you do with indent here. So my personal preference is to fix >>>> indent and accect longer lines. >>> In this case the an often used convention (which is also kind of >>> readable) is to add a newline after the return values, but...

When you have fairly large data, _do not use the formula interface_, as a couple of copies of the data would be made. Try simply: Myforest.rf <- randomForest(Mydata[, -46], Mydata[,46], ntrees=100, mtry=7) [Note that you don't need to set proximity (not proximities) or importance to FALSE, as that's the default already.] You might also want to use

Sarah et. al.: As a matter of aesthetics (i.e. my personal ocd-ness) I prefer using the public API of an object, i.e. *not* to makes use of the representation of a factor as essentially an integer vector with labels, but rather to use its documented behavior. (Feel free to ignore this remark!) Anyway, >cumsum(!duplicated(dat1$B)) [1] 1 1 1 2 2 3 3 3 3 3...

Hi, As I understand, composite primary keys aren''t supported in ActiveRecord yet. May I ask if there are plans for this feature? Better yet, if this feature is under development, how''s the progress going? I''m not trying to use legacy databases. I tend to think that using multiple integer column id''s (composite primary key) are often natural way to

Alternatively, if you can arrive at a sensible ordering of the levels you can declare them ordered factors and make the computation feasible once again. Bill Venables. -----Original Message----- From: r-help-bounces at stat.math.ethz.ch [mailto:r-help-bounces at stat.math.ethz.ch] On Behalf Of Torsten Hothorn Sent: Monday, 5 April 2004 4:27 PM To: David L. Van Brunt, Ph.D. Cc: R-Help Subject:

...---------------------------------- >> ------------ >>>>>>> ---- >>>>>>> >>>>>> >>>> >> >> >> -- >> David L. Van Brunt, Ph.D. >> Outlier Consulting & Development >> mailto: <ocd at well-wired.com> >> >> >> >> > > > ------------------------------------------------------------------------------ > Notice: This e-mail message, together with any attachments, contains > information of Merck & Co., Inc. (One Merck Drive, Whiteh...

...freedreno: move bo-cache to it's own file freedreno: sync uapi freedreno: add madvise support freedreno: fix potential fd leak in error path freedreno: expose kernel driver version freedreno: support either coarse or fine-grained bucket sizes freedreno: ocd freedreno: fix potential leak at free freedreno/msm: use private bo-cache for ringbuffer bo's freedreno/msm: drop return from get_cmd() freedreno/msm: split out cmd buffer tracking from ring list: add first/last entry macros freedreno/msm: split out dump_subm...

...separate line and >> indenting by one tab appears to be the next best solution. Please let me >> know if there's if there's a preferred style for cases like this one. > Readability has IMO higher priority than some limit of 80 chars. > And it hurts readability (at least my OCD) when style changes > as you do with indent here. So my personal preference is to fix > indent and accect longer lines. In this case the an often used convention (which is also kind of readable) is to add a newline after the return values, but before the function name. E.g. something like...

Am 02.02.2015 um 18:07 schrieb Juan Bernhard: > Hello list. I'm thinking to migrate the hole user db from system users > to mysql. I already did it in a test environment, but something is > annoying my OCD... I don't quote the variables username and password > sent to the mysql server. I know, the mysql user that dovecot uses only > has select rights, but it stills bother me, because its possible to do > an useless sql code injection. > > Is there a way to quote that? Something lik...

Several ways: 1. Read ?randomForest, especially the `Value' section. 2. Look at str(myforest.rf). 3. Look at print.randomForest. If the forest has 100 trees, then the mse and rsq are vectors with 100 elements each, the i-th element being the mse (or rsq) of the forest consisting of the first i trees. So the last element is the mse (or rsq) of the whole forest. HTH, Andy > From: David