Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It sounds like you have scalability issues. SQLite has the word "Lite" in it for a reason. It lacks certain things like high concurrency, fine-grained access control, a rich set of built-in functions, stored procedures, esoteric SQL language features, XML and/or Java extensions, tera- or peta-byte scalability, and so forth. I recommend changing databases for starters.</p> <p>I'm also unclear by your question why you would need a 1000 <em>documents</em> in memory all at once and especially 1000 documents with 1000 parts with 1000 more parts, all in memory. I don't know your UI requirements, but in my 15+ years in programming I don't recall ever having to display 1000 of anything on a single web page or form without some sort of paging mechanism, so do you really need to get 1000 * 1000 * 1000 entities from the database all at once?</p> <p>I think you need to take another look at the UI, the current model and the data layer to look for ways to deliver as little content as necessary without sacrificing a lot of performance. Consider using patterns like Lazy Loading, read ahead buffers, caching, paging, search methods, shared static data, etc. to reduce the up-front costs.</p> <p>Think in terms of buying a house. Most of us don't have the money to pay for the house all up front so we get a mortgage. A mortgage is way of spreading out the up-front cost over time. There's a negative impact that comes with all mortgages called interest. Now, instead of shelling out 100,000 my overall cost becomes 250,000 but because I can afford the current payment, I don't really notice the extra 150,000 because the extra cost is absorbed in small increments over time. Also note that I may not even pay back the entire 250,000 if I sell my house in 5 years instead of staying for life of the loan.</p> <p>The point here is that you can spread out the cost of making extra connections to retrieve smaller recordsets and still give the user what they need now. This will reduce the overall up-front costs but will add an additional cost to the individual recordsets being retrieved.</p>
    singulars
    1. This table or related slice is empty.
    1. POUsing multiple ExecuteReader at the same time
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USChris Gessler
    1. USChris Gessler
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks. As commented below, what I don't know is how to split easily the "join" result in the different objects (TranslationUnits, properties)
      singulars
      1. PO
      1. USdavidd00
    2. COOrder by ID and as you loop through the results, keep track of the current ID. When it changes, start a new object.
      singulars
      1. PO
      1. USChris Gessler
    3. COOK. I just guessed there was an easier (or cleaner) way. That one is clear. I'll test it. Thanks
      singulars
      1. PO
      1. USdavidd00
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload