This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hello. Could you please consider adding option of exporting results of the query instead of displaying them in the Grid? Fetching 50 times times 100 records and than doing copy / paste of (very slow) grid does not sound as an option :-) Regards, Dejan
|
|
|
|
|
Excellent idea -- thanks! What sort of format do you envisage? We initially thought CSV, which fits your current "copy and paste" process, but this could be problematic because we don't necessarily know the full set of attributes at the start (there might be an attribute which doesn't appear until the 2000000th item). JSON? XML? Keen to have your feedback. |
|
|
|
|
Either JSON or XML are pretty much good choice. My choice would be XML because there is extensive range of tools which you can use for post-processing.
Regards, |
|
|
|
|
Hi Dejan, We've implemented export to XML for you. If you're on VS2010, the update is available now through the Visual Studio gallery (go to the updates tab in Extension Manager and wait a minute or so for it to find us). If you're on VS2008, it will be included in the next nightly build. Please let us know if you run into any bugs or have any further suggestions! |
|
|
|
|
Thank you, that is exactly what I needed. Just small cosmetic change (for some future version) - add HourGlass cursor while Export is in progress; now VS looks frozen completely while exporting :-) Regards, |
|
|
|
|
Doh! I had remembered to display the wait cursor, but I did it too early and it got reset before we got to the actual export. It should be fixed in the next drop. Thanks for spotting this! |
|
|
|
|
Export to CSV or Excel format would be great. |
|
|
|
|
Hi endempire, We'd be happy to look at this but we'd like to hear a bit more about how you envisage it working. One issue with CSV is that the set of attributes is not known when we start the export. This makes it a bit tricky to write the CSV header row if the file is very large (if it's small, we can just collect the list of attributes, reopen the CSV file and insert the header row at the beginning -- but inserting at the beginning of a very large file is a bit trickier). Worse still, it means we can't easily put the same number of items on each line e.g. if the first 99999 items we retrieve have attributes A and B, but the 100000th has attribute C, do we have to go back and emit an additional separator into each of the first 99999 items? (This might not be an issue if we exported directly to Excel.) I assume you need a header row, but do you also need to have blanks emitted for 'missing' attributes? Another problem, which affects both Excel and CSV, is what to do with multi-value attributes, e.g. if an item has two A attributes. We can't concatenate the values because we don't know the order, but I'm not sure it makes sense to emit them as separate columns either (especially since if other items also have two A attributes then this might give the impression that the grouping into columns is deterministic, which it isn't). Should this be an error, or would it be okay to just emit them as separate columns and let the user sort out what do do with those columns? Thanks for your feedback! |
|
|
|
