Re: [zeta-dev] Documentation
Hi Gaetano On Tue, Jan 11, 2011 at 10:15 PM, Gaetano Giunta giunta.gaet...@gmail.com wrote: To me, the way the components work often feels like blackmagick: sometimes it is logical, but more often it's just like incantations. The example spells given in the docs are fine, but as soon as you stray a little bit from those, you're on your own - either it works at the very first try or it becomes a thankless test/change/repeat loop (eg. sometimes a certain mix of options work, and another mix does not work, or some methods have to be invoked in a particular order). Looks like a hacker thing :D Isn't that how pretty much all libs, frameworks, and programming languages work in general ? What lib/program/framework does it better than the components and why ? Regards James -- http://jamespic.info Customer is king - Le client est roi - El cliente es rey.
Re: [zeta-dev] Documentation
Hi all, On Wed, Jan 12, 2011 at 8:46 AM, Christian Grobmeier grobme...@gmail.com wrote: - a method that can be used to easily debug the code. ... For example, I use PersistentObject and I would like to know why the find query returns me nothing. In the documentation, there's no clue to that could help me to resolve my probleme. And also, there's no way to print the $q-getQuery() without hacking PersistentObject. Isn't it possible by just setting a breakpoint and without hacking ? Maybe we must consider the fact to create a false dependancy to Debug, disabled by default. What would be the benefits of that over xdebug ? I insist for your own good, maybe the source of your problem is not specific to the components... are you sure you're using xdebug correctly ? Regards James -- http://jamespic.info Customer is king - Le client est roi - El cliente es rey.
Re: [zeta-dev] Search Component
On Wed, 12 Jan 2011, Maxime Thomas - Wascou wrote: My point was very simple, I've got messages to index with a class like id (int), message (string). In SolR, I've defined in my core, only this two fields with id as uniqueKey and message as defaultSearchField. At first, I did not set up SolR to use dynamic fields. There were two problems : - first, another field was added : ez_search_field_s and I don't why. - second one, all my fields were automatically suffixed by there type... which wasn't the SolR type. Do you know why we have the ez_search_field_s added ? It was part of your definition then. Why all the field are suffixed (with wrong types) ? Is it the normal way or did I miss something ? WHy is it a wrong type? All fields are suffixed by their type. In order for the Search component to work, you need a specific base schema.xml for Solr: http://incubator.apache.org/zetacomponents/documentation/trunk/Search/tutorial.html#id1 and schema: http://incubator.apache.org/zetacomponents/documentation/trunk/Search/solr_schema.html cheers, Derick -- http://derickrethans.nl | http://xdebug.org Like Xdebug? Consider a donation: http://xdebug.org/donate.php twitter: @derickr and @xdebug
