There is a 1-[0,1] relationship between Person and Address with address_id
being the nullable foreign key.
I think you should be good with single query/entity then (no need for
nested entities)
entity name=person query=select person.id, person.name,
person.address_id, address.zipcode from
Guys???
You are in the wrong thread. Please, send a message to the mailing list, do
not answer to existing posts.
Thank you.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-and-Nutch-Droids-to-use-or-not-to-use-tp890640p892041.html
Sent from the Solr - User mailing
I'm putting together an entity. A simplified version of the database schema is
below. There is a 1-[0,1] relationship between Person and Address with
address_id being the nullable foreign key. If it makes any difference, I'm
using SQL Server 2005 on the backend.
Person [id (pk), name,
This is a slow way to do this; databases are capable of doing this
join and feeding the results very efficiently.
The 'skipDoc' feature allows you to break out of the processing chain
after the first query. It is used in the wikipedia example.
http://wiki.apache.org/solr/DataImportHandler
On
this looks like a common problem. I guess DIH should handle this more
gracefully. Instead of firing a query and failing it should not fire a query
if any of the values are missing . This can b made configurable if needed
On Sun, Jun 13, 2010 at 9:14 AM, Lance Norskog goks...@gmail.com wrote:
