Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your posted code reads the entire file and builds a copy of the file in memory as a single list of all the file contents split into tuples, one tuple per line. Since you ask about how to use less memory, you may only need a generator function:</p> <pre><code>def readfile(filepath, delim): with open(filepath, 'r') as f: for line in f: yield tuple(line.split(delim)) </code></pre> <p>BUT! There is a major caveat! You can only iterate over the tuples returned by readfile once.</p> <pre><code>lines_as_tuples = readfile(mydata,','): for linedata in lines_as_tuples: # do something </code></pre> <p>This is okay so far, and a generator and a list look the same. But let's say your file was going to contain lots of floating point numbers, and your iteration through the file computed an overall average of those numbers. You could use the "# do something" code to calculate the overall sum and number of numbers, and then compute the average. But now let's say you wanted to iterate again, this time to find the differences from the average of each value. You'd think you'd just add another for loop:</p> <pre><code>for linedata in lines_as_tuples: # do another thing # BUT - this loop never does anything because lines_as_tuples has been consumed! </code></pre> <p>BAM! This is a big difference between generators and lists. At this point in the code now, the generator has been completely consumed - but there is no special exception raised, the for loop simply does nothing and continues on, silently!</p> <p>In many cases, the list that you would get back is only iterated over once, in which case a conversion of readfile to a generator would be fine. But if what you want is a more persistent list, which you will access multiple times, then just using a generator will give you problems, since you can only iterate over a generator once.</p> <p>My suggestion? Make readlines a generator, so that in its own little view of the world, it just yields each incremental bit of the file, nice and memory-efficient. Put the burden of retention of the data onto the caller - if the caller needs to refer to the returned data multiple times, then the caller can simply build its own list from the generator - easily done in Python using <code>list(readfile('file.dat', ','))</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. POPython - Best way to read a file and break out the lines by a delimeter
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPaulMcG
    1. USPaulMcG
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPython - Best way to read a file and break out the lines by a delimeter
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COBrilliantly explained Paul!
      singulars
      1. PO
      1. USMatt Alcock
    2. COI guess you could always just create another generator. `newlines_as_tuples = readfile(mydata,',')`
      singulars
      1. PO
      1. USMatt Alcock
    3. COAbsolutely, assuming it's cheaper to create the generator than a retaining list - this is probably the case for reading from a file, but if it the generator was yielding rows from a database, or data from a webserver, I'm not so sure.
      singulars
      1. PO
      1. USPaulMcG
 

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