On Wed, Sep 29, 2010 at 11:34 AM, Andy Chambers <achambers.h...@gmail.com> wrote: > Hi, > > I've got a nice normalized table and need to produce a de-normalized > view of this table (i.e. convert it > from tall skinny, into wide short table). In order to do this, I was > planning on just joining the > table to itself for each "value" that needs to be turned into a > column. However, it turns out there's > 96 values so I run into the "only 64 tables in a join" constraint. Is > there another idiom for > doing this sort of transformation or should I just use two helper > tables with 33 values in each and > then join them. > > For those who have used other databases, is it quite common to have > this constraint? This seems > like it would be quite a common problem in ETL projects (admittedly > it's perhaps unusual to be > using sqlite for an ETL project). > > Hope I've made myself clear.
You would make yourself even clearer if you gave the schema for both the source and the desired target tables. > > Cheers, > Andy > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Puneet Kishor _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
