Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POHow to use multiprocessing with class instances in Python?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. US9000
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to use multiprocessing with class instances in Python?
      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. COThat doesn't work...I get the error "AttributeError: 'ProcessWorker' object has no attribute 'run_long_command'". I wouldn't expect that to work since ProcessWorker has none of the methods that exist in the Worker class. I want to send the method over the pipe (with state information) so that the remote process can make use of all of that state information. I really don't see the point of the multiprocess module if all it will do is run stateless function on the other side.
      singulars
      1. PO
      1. USDavid Lynch
    2. COI'm sorry, but I have to repeat. You _can not_ send a method over the pipe. This is why `pickle` complains about it. Sending executable code is not impossible, but it gets _much_ more involved that just deserializing a code object. You should implement the methods you want to run in Worker class beforehand. If you do need to send code not know in advance, your best bet is sending Python source as a string, then calling `compile` and `eval` on it. If you want to send a method with a state, put all the state into method's arguments, or use a shared database.
      singulars
      1. PO
      1. US9000
    3. COWRT running stateless methods: you have pipes that can hold the state. You parcel out your initial state to several processes, then collect the results back. If you want highly shared state (e.g. geometry for ray tracing), you use an (in-memory) database, anything from memcached to a regular RDBMS. Using global _mutable_ state is usually a bad enough idea. If you have to, use an arbiter process that reads from pipes and resolves conflicts (e.g. a database).
      singulars
      1. PO
      1. US9000
 

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