Datamapper DataMapper → 1.1.1

Comments and changes to this ticket

• You flagged this item as spam.
  

  Dan Sully June 18th, 2010 @ 01:15 AM

  • Tag set to “dm-core sub-query”
  • Assigned user set to “Dan Kubb (dkubb)”

  See

  https://gist.github.com/8d3eb5702cb12c666e5f

  for a test case.

• 

  Dan Kubb (dkubb) June 18th, 2010 @ 01:20 AM

  • Tag changed from “dm-core sub-query” to “dm-core, mysql-adapter, sub-query”

  This seems to be a bug in the MySQL adapter. Works in SQLite.

• 

  Dan Kubb (dkubb) September 7th, 2010 @ 08:54 PM

  • Milestone changed from “1.0.2” to “1.1”
  • Tag changed from “dm-core, mysql-adapter, sub-query” to “dm-core, mysql-adapter, sub-query”
  • Milestone order changed from “0” to “0”
• 

  Dan Kubb (dkubb) January 16th, 2011 @ 09:08 PM

  Dan, I just tried this with SQLite and MySQL and both seemed to return the same record. MySQL does use two queries, but it still returns the same results. Is there something wrong, or has this bug been fixed in the master branch?

  BTW: The reason for two queries is that code that generates SELECT also handles subselects for the WHERE clauses in DELETE, UPDATE. Those statements will not allow the subselect to reference the table being deleted from. Until the code can be split out, or refactored to not include the target table in the subselect, we have to materialize the intermediary collection instead of use subselects.

• 

  Dan Kubb (dkubb) March 16th, 2011 @ 10:41 PM

  • Milestone changed from “1.1” to “1.1.1”

  [bulk edit]