similar to: Sum/Aggregate at database level or in rails controller?

Hello sanjay! Well, the error-message does also include the solution: a C-compiler is missing on your machine - or at least it's not included in the path-variable. Without one you can't compile samba yourself. Maybe then you want to get some pre-compiled binaries? Is an C-compiler installed on your system? If not, istall one and make sure it could be found by the path-variable so that

Hello everyone, Nice to meet you all, am new to the forum. I''m stuck with rake / actionmailer trying to display a set of found records. We have a simple actionmailer rake task that is supposed to send a daily email digest of tasks that are due for a specific user. So far, it''s working but the email only displays the first message. In my task model scope :tasksdue, lambda {

I have a table of companies and a join table forming the relationship between a list of possible services they can provide. Working from a basic understanding of OOP I assumed that there should be a series of Serviceprovider child objects of the company class. Company < ActiveRecord::Base has_belongs_to_many :services end Serviceprovidertype1 < Company Serviceprovidertype2 <

Hi, Sorry for the confusion. I would like to estimate a model wherein the marginals of z with respect to w1 and w2 are smooth functions of x and y. I have data on z, x, y, w1 and w2. so E[dz/dw1] = f(x,y) and E[dz/dw2] = g(x,y) and I would like to estimate f(x,y) and g(x,y) I suppose I could try to fit something more general using projection pursuit, but the nature of the problem suggests

Hi R-devel, I am facing a situation where the number of options I would like to propose to the user is somewhat big (and could easily increase more and more as I will code up a little more - even coming to a point where an user should be able to implement his own options). What we have to handle options is the couple: options(par=value) and getOption("par") I was aking myselft what

Thanks David for the comments. Sorry for the late reply. On Mon, Aug 23, 2010 at 11:52 PM, David A. Greene <greened at obbligato.org> wrote: > Che-Liang Chiou <clchiou at gmail.com> writes: > >> Hi there, >> >> Thank Nick for kindly reviewing the patch.  Here is the link to the >> source code of the PTX backend; it would help Nick review the patch.

Hi there, Thank Nick for kindly reviewing the patch. Here is the link to the source code of the PTX backend; it would help Nick review the patch. http://lime.csie.ntu.edu.tw/~clchiou/llvm-ptx-backend.tar.gz The source code from above link is a working prototype. So it will not be upstreamed as is; I will refactor and add unimplemented features while upstreaming it. That said, the source code

Hadley, Looks interesting and like a fun project from what you said in the email (I don't have time right now to dig deep into the readme) A few thoughts. First off, you are using the word "type" throughout this email; You seem to mean class (judging by your Date and factor examples, and the fact you mention S3 dispatch) as opposed to type in the sense of what is returned by

Che-Liang Chiou <clchiou at gmail.com> writes: > Hi there, > > Thank Nick for kindly reviewing the patch. Here is the link to the > source code of the PTX backend; it would help Nick review the patch. > http://lime.csie.ntu.edu.tw/~clchiou/llvm-ptx-backend.tar.gz Great! > I decided to take the code generator approach (referred to as codegen > approach) rather than C

Hi, I want to automate somewhat the addition of created_by/updated_by fields on my models (i.e. to include username). What''s the best/recommended way to do this? Would it be to: a) Find out how to extend the ActiveRecord::Base itself (I haven''t extended a class before yet) b) Use a plugin type approach where you have to add a tag manually to each model file which then

> First off, you are using the word "type" throughout this email; You seem to > mean class (judging by your Date and factor examples, and the fact you > mention S3 dispatch) as opposed to type in the sense of what is returned by > R's typeof() function. I think it would be clearer if you called it class > throughout unless that isn't actually what you mean (in