search for: uglyness

I was brainstorming today about a smooth way to define conditions in an sql query, when the numbers of attributes increase, so does the uglyness. So instead of passing a hash, I thought you could specify the conditions directly in code. I hacked together some example code which actually turned out to work. The result is concise and pretty beutiful. def search(params) Ad.find(:all) do |conditions| conditions.area_id = params[:area_id]...

...se we currently don't allow this kind of thing in the IR at all, so this would be a pretty major change. I'd like to solicit some opinions on the best way to represent this in the IR (in particular whether it's worth introducing a way to annotate AA MD on function arguments to avoid the uglyness of introducing 2N extra metadata tags). Thanks, Keno

...on I also want to go back and set the value of the created_at and updated_at columns for the previous rows. What is the best way to do that? Initially I thought I was being smart and decided to put an UPDATE SQL query in a find_by_sql statement and then I could not deal with it''s uglyness. Any much wiser suggestions? John Kopanas http://www.kopanas.com ============================================================ http://www.soen.info - Index of online software engineering knowledge http://www.cusec.net - Canadian University Software Engineering Conference http://www.soenlive.co...

...ecause this server runs an NTP daemon. A little searching for this problem shows that it is an issue with the Linux kernel gettimeofday(), see e.g. http://lkml.org/lkml/2007/8/23/96 Below is a patch (untested) to work around this issue. Do you see something wrong with this approach, apart from the uglyness? I just picked the 4395-4400 values by chance. Can you figure out how big the window should be? Thanks, Anders. --- ./src/lib/ioloop.c-orig 2008-06-20 10:45:54.000000000 +0200 +++ ./src/lib/ioloop.c 2008-06-20 10:47:36.000000000 +0200 @@ -230,8 +230,13 @@ struct timeval tv, tv_call;...

...reated as signed), and a few other things. The other things include basically any type that can hold any other type, from arrays to structs and so forth. It was easy enough, I had made on the order of a crap-ton of static_visitors to handle the variant in all its very fast, but still overwhelming uglyness. I have got to the point where I need need to represent the function type, this has suddenly introduced a whole new class of uglyness to handle as the types can propagate into the blocks and so forth. I am just wondering if I am missing some very simple way to handle this. Such as, is there any...

How can I get a list of all model classes in the domain of a Rails application (all models, both in "app/models" and in components/somedir/model.rb)? Thanx in advance for your precious help! Edoardo "Dado" Marcora

I''m looking to implement model inheritance in a new application. Is there any good alternative to single-table-inheritance? -- -Alder

Hi, My recent refactoring of the (machine-dependent) use of <alloca.h> does not attempt to change CWriter's behavior of emitting a #include for <alloca.h>. FreeBSD does not have <alloca.h>, so this would cause trouble. We could change it to emit an #ifndef __FreeBSD__...#endif around #include <alloca.h>. I suggest this because, I'm guessing, whether or not the

Hello friends, I'm having a problem with my home server (ASUS A7V133 motherboard) which has a horrible performance with ATA disks connected to an integrated promise controller. Below you can see iozone results of the same disk connected to the primary/ secondary controller versus the promise one. Promise ATA100 controller: ========================= Version 1.02a ------Sequential

...tream name, which when we get here we know we've already > + * done. So we have to call the stat or lstat VFS calls > + * directly here. Else, a base_name that contains a ':' (from a > + * demangled name) will get split again. > + * > + * FIXME. > + * This uglyness will go away once smb_fname is fully plumbed > + * through the VFS. > + */ > + ret = vfs_stat_smb_basename(handle->conn, > + smb_fname, > + sbuf); > + if (ret == -1) { > + return map_nt_error_from_unix(errno); > + } > + } > + > + return N...

On Fri, Aug 26, 2016 at 06:33:26PM +0200, Ralph Böhme via samba wrote: > On Thu, Aug 25, 2016 at 12:14:00PM -0700, Jeremy Allison wrote: > > On Wed, Aug 24, 2016 at 04:06:42PM +0200, Ralph Böhme via samba wrote: > > > > > > Yeah, as much as I'd like to avoid adding a new option, I guess we > > > have to do something about it, my latest take on this is >

...tream name, which when we get here we know we've already > + * done. So we have to call the stat or lstat VFS calls > + * directly here. Else, a base_name that contains a ':' (from a > + * demangled name) will get split again. > + * > + * FIXME. > + * This uglyness will go away once smb_fname is fully plumbed > + * through the VFS. > + */ > + ret = vfs_stat_smb_basename(handle->conn, > + smb_fname, > + sbuf); > + if (ret == -1) { > + return map_nt_error_from_unix(errno); > + } > + } > + > + return N...

On Fri, Aug 26, 2016 at 04:03:49PM -0700, Jeremy Allison wrote: > On Fri, Aug 26, 2016 at 02:46:19PM -0700, Jeremy Allison via samba wrote: > > On Fri, Aug 26, 2016 at 06:44:05PM +0200, Ralph Böhme wrote: > > > > > > Cheerio! > > > -slow > > > > Still reviewing this - but a few things that will need changing: > > > > When adding the