StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POLaravel 4, unit tests, extra data returned
primarykey
Id
18840666
data
AcceptedAnswerId
18845744
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-17T03:04:06.800
FavoriteCount
0
LastActivityDate
2013-09-17T09:11:35.897
LastEditDate
LastEditorUserId
0
OwnerUserId
388783
ParentId
0
PostTypeId
1
Score
0
ViewCount
190
LastEditorDisplayName
text
Body
bros. Got a strange behaviour. I'm writing tests for my Laravel 4 <a href="https://github.com/franzose/ClosureTable" rel="nofollow">ClosureTable</a> package. All tests create new <code>Entity</code> (or <code>Entitites</code>) for further use. For example, one of the first tests: <code>ClosureTableTestCase::testInsertSingle</code>. When I run it, I got this: <code> Exception: SQLSTATE[HY000]: General error: 1 table pages_closure has no column named 0 (SQL: insert into "pages_closure" ("ancestor", "depth", "descendant", "0", "1", "2") values (?, ?, ?, ?, ?, ?)) (Bindings: array ( 0 => '1', 1 => '0', 2 => '1', 3 => '1', 4 => '1', 5 => '0', ))</code> And <code>var_dump</code> says me the following: <pre> array(1) { [0] => array(6) { 'ancestor' => string(1) "1" [0] => string(1) "1" 'descendant' => string(1) "1" [1] => string(1) "1" 'depth' => string(1) "0" [2] => string(1) "0" } } </pre> However when I create an Entity via web interface, all's fine! Errors come from <code>DB::select($selectQuery);</code> call when I run tests via terminal. As you can see, I somehow got [0], [1], and [2] extra array keys. However when I create an Entity via web interface, all's fine! Error is in this method that's run internally: <pre><code>protected function performInsertNode($descendant, $ancestor) { $table = $this->closure; $ak = static::ANCESTOR; $dk = static::DESCENDANT; $dpk = static::DEPTH; DB::transaction(function() use($table, $ak, $dk, $dpk, $descendant, $ancestor){ $selectQuery = " SELECT tbl.{$ak} as {$ak}, {$descendant} as {$dk}, tbl.{$dpk}+1 as {$dpk} FROM {$table} AS tbl WHERE tbl.{$dk} = {$ancestor} UNION ALL SELECT {$descendant}, {$descendant}, 0 "; $results = DB::select($selectQuery); array_walk($results, function(&$item){ $item = (array)$item; }); var_dump($results); DB::table($table)->insert($results); }); } </code></pre> Do you can point me out a mistake?
Tags
<php><unit-testing><laravel>
Title
Laravel 4, unit tests, extra data returned
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USfranzose
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.