On 09/13/2013 06:04 AM, Ricardo Aráoz wrote:
OTOH, I also tried getting rid of the addFields and there was a
problem with the alias. In my structure there are many fields (in
different tables) called "Nombre". I use alias when I need to include
their lookup in some other bizobj. When I did this the framework got
confused and showed me the wrong "Nombre" in the calculated field. So
as much as I hate doing the same thing twice (addFrom and DataSource)
it looks like the safest way to go.
In my .addFields() I do things like this:
self.addField("escounty.cname as countyname")
where escounty is from a .addJoin()
I think I saw someone use complete SQL statements - in the .addField() as in
.addField("select some_field from some_table where something as newField")
I can't recall where I saw it. I've been reading a lot of C++ code
lately and maybe I'm mixing codes. So I would check before I used it.
Johnf
_______________________________________________
Post Messages to: Dabo-users@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/5233101c.50...@jfcomputer.com
