I have a cool schema, which uses both column aggregation and concrete table inheritance, and a simple search engine to develop, which needs to search the field title ( or name ) of every entity, regardless its definition.
This means, for example, that it has to look for the query ( Es. “John” ) in the
sfGuardUser model, matching the name column, and also in the
Post model, matching the title column.
Worthless to say, I got something like 15 tables: not that much, neither a couple.
Solution: use Lucene
Yes, I know: Lucene ( or Solr ) would be the best way to do that; but I can’t use it as I forced myself not to use Lucene every time I need a search engine that simple. I need to search for a single word, in 15 tables, between something like 400 records.
Lucene would swear at me if I use it for this kinda purposes.
Solution2: be a column-aggregation-holic
Another time: I can’t.
The whole schema has different and various fields so I cannot stand a full-of-null record set.
Here’s how I “solved” it, with UNIONs and a custom pagination.
Alex, CTO @ DNSEE, said the drawbacks of this approach are justified by the poverty of the SE.
Breaking the concept of fat models and thin controllers, I fulfilled my controller with the following code…
First step: build the UNION
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Execute the query
1 2 3
Prepare the paginator
1 2 3 4 5 6
In the view you will only need to render $items and print the pagination:
1 2 3 4 5