Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First, I will admit that I have not read thru this issue thoroughly, but I have gut feeling and a suggestion. I have seen issues like this and they typically happen in large legacy applications with many models, some of which have a connection pool to another database. In said scenario it is easy to reference a model that uses another connection during ActiveRecord's callback phase. This leads to cross database transactions which is not supported by ActiveRecord out of the box. </p> <p>If you think this may be the cause review your code for the following. Make sure that you never use #establish_connection and if you do, only use it once in a base or connection class that others inherit from. I have a github gist here (<a href="https://gist.github.com/metaskills/4065702" rel="nofollow">https://gist.github.com/metaskills/4065702</a>) that shows what I am talking about. Second, make sure that your models are not talking to another model in another connection pool during save/transactions.</p>
    singulars
    1. This table or related slice is empty.
    1. POData loss after deadlock - SQL Server 2008, Ruby on Rails, Apache, Phusion Passenger, Linux, FreeTDS
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMetaSkills
    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. COThis was not the problem in my case. I really tracked it down to the problem that at one point the value of @@TRANCOUNT was taken from the cache where it should have selected it from the database (see my own response above). So it returned 0 where it should have been 1, and as a consequence a transaction was not committed.
      singulars
      1. PO
      1. USsys64738
    2. COThis <code>CACHE (0.0ms) SELECT @@TRANCOUNT</code> should never happen. The 2.3 adapter codebase uses the #info_schema_query helper does not do what it really should. In the 2-3-stable branch, it is concerned with logging. To see what I mean, take a look at the latest 3-2-stable/master code. There is a changelog that mentions how we now properly use the `SCHEMA` name argument in DB queries that are for reflection and schema related. This means they are not cached also. So... if you wanted to patch the 2-3-stable branch, maybe something like this https://gist.github.com/metaskills/5387936
      singulars
      1. PO
      1. USMetaSkills
    3. COThanks for your comment! I have tried adding the "SCHEMA" argument. With the first call, the log (I locally changed the code that is supressing the logging for this) is now showing `SCHEMA (0.5ms) SELECT @@TRANCOUNT`. But the second time I still get the `CACHE (0.0ms) SELECT @@TRANCOUNT` line, and the error occurs again (maybe the SCHEMA thing is Rails 3.x specific?). I have now tried changing the line to `trancount = uncached { select_value("SELECT @@TRANCOUNT") }`, which seems to fix the problem.
      singulars
      1. PO
      1. USsys64738
 

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