Am new to EF and am trying to understand the updated concepts as am getting old data to use EFextensions etc..(mostly) when I search in Google.
Am trying to execute a SQL query using ExecuteStoreQuery.
I have something called MergeOption. What exactly does it do?
I have read http://msdn.microsoft.com/en-us/library/system.data.objects.mergeoption.aspx
But am not understanding it clearly. Some examples will take me through.
Thanks,
Peru
Specifying the MergeOption with ExecuteStoreQuery allows you to determine how results will be tracked as entities. As you read in the article you referenced, there are four options:
AppendOnly (default)
OverwriteChanges
PreserveChanges
NoTracking
Here are a couple of links (basic example, detailed example) that show some in-depth examples of MergeOption is use, and its impact on the objects being tracked.
Related
Joomla4 is challenging me significantly. With a lack of almost any useful documentation and a day nearly wasted in trying all sorts of things, I am forced to ask:
How to add Article's Custom Fields into Joomla4 Template?
I have used:
use Joomla\Component\Fields\Administrator\Helper\FieldsHelper;
And I have tried a significant number of tests with various code found splattered across the internet. I have looked this: https://joomla.stackexchange.com/questions/31489/how-to-get-call-joomla-4-custom-fields-into-module
And I have tried so many options, I have lost count of what I have and have not tested.
My only result is that I can list out the fields that are assigned to the article. But I can not, for the life of me, work out how to then get the value of those fields for that article ID.
I have looked at: \components\com_fields\layouts\fields\render.php
But I can't work out where/how/when the variable "$displayData" gets set. Or how to set it.
Thank you in advance.
I'm trying to use the ABPerson method searchElementForProperty:... to create a moderately complex search. In particular, I want to find the set of people who have an email address that ends with "foo.com", and are NOT part of the pre-populated group "My workunit".
Matching against just the email address seems to be trivial. Creating a conjunction against the (inverse of the) group membership seems impossible.
Yes, I can do this by doing the obvious explicit cross-checking myself, but if the point of having search functionality directly in Address Book is to optimize performance, wouldn't it make sense for the search facility to be sufficiently complete to be able to do this?
Thanks in advance,
Tony
You could potentially copy all the data from the address book into a Core Data store and use predicates to work with that data. Predicates tend to be very useful when building complex queries.
Predicate Programming Guide
In this case you would have to get all contacts ([[AddressBook sharedAddressBook] people]) and also have a Core Data entity called Contact (or something similar) that would save names, emails, addresses and other properties from the ABPerson object.
Having this you can probably create an NSPredicate to filter with the conditions you want.
Groups reference their members according to recordId. The only way I have found to perform such an operation is here: how to find parent groups of a person. It is not a simple thing like we would like. It seems that Apple is not concerned about group searching which would be extremely useful.
Let's say I search for "ABLS" and the SOLR returns a result that to me does not make any sense.
How can I debug why SOLR picked this record to be returned?
debugQuery=true would help you get the detailed score calculation and the explanation for each scores.
An over view of the scoring is available at link
For detailed explaination of the debug information you can refer Link
You could add debugQuery=true&indent=true to the url and examine the results. You could also use the analysis tool in solr. Go to the admin and click analysis. You would need to read the wiki to understand either of these more in depth.
queryDebug will give you knowledge about why your scoring looks like it does (end how every field is relevant).
I will get some results that you are not understand and play with them with Solr's analysis
You should find it under:
/admin/analysis.jsp?highlight=on
Alternatively turn on highlighting over your results to see what is actually matching in your results
Solr queries are full of short parameters, hard to read and modify, especially when the parameters are too many.
And after it is even harder to debug and understand why a document is more or less relevant than another. The debug explain output usually is a three too big to fit in one page.
I found this Google Chrome extension useful to see Solr Query explain and debug in a clear manner.
For those who still use very old version of solr 3.X, "debugQuery=true" will not put the debug information. you should specify "debugQuery=on".
There are two ways of doing that. First is the query level, which means adding the debugQuery=on to your query. That will include a few things:
parsed query
debug timing information
detailed scoring information which helps you with analysis of why a give document is given a score.
In addition to that, you can use the [explain] transformer and add it to your fl parameter. For example ...&fl=*,[explain], which will result in your documents having the scoring information as another field.
The scoring information can be quite extensive and will include calculations done by the similarity algorithm. If you would like to learn more about the similarities and the scoring algorithm in Solr, have a look at this my and my colleague Radu from Sematext talk from the Activate conference: https://www.youtube.com/watch?v=kKocQdYGVJM
For example, when using entity.name in NSPredicate, I needed to change setFetchPredicate to setFilterPredicate, the 1st one was working just fine with XML store, SQLite required 2nd one.
I found: this message but couldn't find anything related in the list archive.
Is there any list with all valid NSPredicate statements?
When garbage collection can cause troubles?
See the section titled "Fetch Predicates and Sort Descriptors" of the Core Data Programming Guide for SQLite-specific limitations.
I'm not aware of any Core-Data-specific limitations in a Garbage-Collection-enabled environment - the reference in the e-mail you posted is news to me. A quick Google search revealed this thread and it's the first I'm hearing of this issue. I certainly never encountered it despite having a similar setup in a compute-intensive app that used Core Data + SQLite store type.
You'll need to be a lot more specific about your first question, however. I'm not sure what you mean.
I would like to represent data that gives an overview but allows them to drill down in an inline fashion - so if you had a grouping of say 6 objects the user could expand the data and it would show the 6 objects immeadiately below it before any more high level data.
It would appear that MSHFlexgrid gives this ability but I can't find any information about actually using it, or what it's limitations are (can you have differing number of fields and/or can they have different spacing, what about column headers, indentation at for the start, etc).
I found this site, but the images are broken (in ie8 and ff3.5). Google searches show people just using the flat data representation but nothing using the hierarchical properties). Does anyone know any good tutorials or forums with a good discussion about pitfalls?
Due to lack of information about using it, I am thinking of coding my own version but if anyone has done work in this area I haven't found it - I would of thought it would be a natural wish for data representation. If someone has coded a version of this (any language) then I wouldn't mind reading about it - maybe my idea of how to do it wouldn't be the best way.
You might want to check out vbAccelerator. He has a Multi-Column Treeview control that sounds like what you may be looking for. He gives you the source and has some pretty decent samples.
The MSHFlexGrid reference pages and the "using the MSHFlexGrid" topic in the Visual Basic manual?
Sorry if you've already looked at these!