Databases
StackOverflow2013
Postsdbo
POPOST Request too slow in Rails
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPOST Request too slow in Rails
    primarykey
    data
    text
    <p>In my distribuited application the client must send a set of photo. The post is like this:</p> <pre><code>res = Net::HTTP.post_form(URI, :mac =&gt; macyaml, :value =&gt; fileyaml, :created_at =&gt; createyaml, :num =&gt; N) </code></pre> <p>where macyaml, fileyaml e createyaml are the yaml codified file about the array of photo information.</p> <p>the log server is like this:</p> <pre><code>Started POST "/events/save_photo_2" for 192.168.0.113 at 2012-04-11 09:40:00 +0200 Processing by EventsController#save_photo_2 as */* Parameters: {"value"=&gt;"[FILTERED]", "mac"=&gt;"[FILTERED]", "data_type"=&gt;"[FILTERED]", "created_at"=&gt;"[FILTERED]", "name"=&gt;"photo", "num"=&gt;"19"} WARNING: Can't verify CSRF token authenticity (0.3ms) SET PROFILING=1 Device Load (1.2ms) SELECT SQL_NO_CACHEdevices.* FROMdevicesWHEREdevices.mac` = '000DC5D33AFB' LIMIT (0.3ms) BEGIN SQL (2.6ms) INSERT INTO multimedia (created_at, data, device_id, event_id, updated_at) VALUES ('2012-04-11 09:33:57', x'666e4d7a2a2ecffd...', 13, NULL, '2012-04-11 09:40:00') (29.2ms) COMMIT (0.3ms) BEGIN SQL (0.8ms) INSERT INTO events (created_at, data_type, device_id, element_id, multimedia_id, name, status, updated_at, value) VALUES ('2012-04-11 09:33:58', 'image', 13, 55728, 316599, 'photo', NULL, '2012-04-11 09:40:00', '--- --\n...\n') (26.3ms) COMMIT ... ... ... (0.4ms) BEGIN SQL (2.4ms) INSERT INTO multimedia (created_at, data, device_id, event_id, updated_at) VALUES ('2012-04-11 09:34:33', x'666e4d7a2a2ecffd5a7123e2ac1d8f...', 11, NULL, '2012-04-11 09:40:06') (33.1ms) COMMIT (0.3ms) BEGIN SQL (0.8ms) INSERT INTO events (created_at, data_type, device_id, element_id, multimedia_id, name, status, updated_at, value) VALUES ('2012-04-11 09:34:33', 'image', 11, 56127, 316635, 'photo', NULL, '2012-04-11 09:40:06', '--- --\n...\n') (25.7ms) COMMIT (0.3ms) BEGIN (0.4ms) SET PROFILING=1 (1.1ms) SELECT SQL_NO_CACHE 1 FROM devices WHERE (devices.mac = BINARY '000DC5D33AFB' AND devices.id != 13) LIMIT 1 (1.0ms) UPDATE devices SET elem_photo_id = 55746, updated_at = '2012-04-11 09:40:02' WHERE devices.id = 13 (32.9ms) COMMIT Rendered events/save_photo_2.html.erb (0.2ms) Completed 200 OK in 2644ms (Views: 14.7ms | ActiveRecord: 1732.3ms)` </code></pre> <p>someone could explain me what's the warning:</p> <pre><code>WARNING: Can't verify CSRF token authenticity </code></pre> <p>and what's the COMMIT time? how can i reduce this?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMatthias Männich
    1. USDabidi
    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. POPOST Request too slow in Rails
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COMy eyes started to bleed when I've tried to read this. Could you please work on a better format of your question?
      singulars
      1. POPOST Request too slow in Rails
      1. USErnest
    2. COedited.... is it better? ;-)
      singulars
      1. POPOST Request too slow in Rails
      1. USDabidi
    3. COUse {code} for your log content, or even better delete it, becuase it gives no value at all. COMMIT time, is the the time in milisecods of last insert action to the database. And about CSRF token, this was already answered hundreds of times, just quick search in google and you will find many sources.
      singulars
      1. POPOST Request too slow in Rails
      1. USErnest
 

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