StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POLaravel Migrations - Table Prefix Issue
primarykey
Id
15885681
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
9
CommunityOwnedDate
CreationDate
2013-04-08T17:54:10.067
FavoriteCount
2
LastActivityDate
2013-04-28T10:19:43.790
LastEditDate
2013-04-10T14:04:28.360
LastEditorUserId
941570
OwnerUserId
941570
ParentId
0
PostTypeId
1
Score
2
ViewCount
5947
LastEditorDisplayName
text
Body
I'm building a dummy site to test Laravel 3.x. I'm creating my site migrations right now. Everything was doing just fine until the following error showed up: <pre><code>SQLSTATE[42s02]: Base table or view not found: 1146 Table 'databasenamehere.prefix_laravel_migrations' doesn't exist </code></pre> The issue is that laravel all of a sudden started to prefix the 'laravel_migrations' table (when it is supposed to do it only with the other ones). I wonder if I'm doing something wrong or if it is a known issue. I'm trying to run the following migration (using the php artisan migrate application command): <pre><code>public function up() { Schema::create('siteinfo', function ($table) { $table->engine = 'InnoDB'; $table->string('name'); $table->string('title')->nullable(); $table->string('corp_name')->nullable(); $table->string('corp_addr')->nullable(); $table->string('corp_phone')->nullable(); $table->string('corp_city')->nullable(); $table->string('corp_state')->nullable(); $table->string('corp_email')->nullable(); $table->string('main_url')->nullable(); $table->timestamps(); }); } </code></pre> Any help would be great. EDIT 1: <ul> <li>I noticed some minutes ago that my tables got no prefix at all, even with the "prefix" configuration set correctly on the config/database.php file.</li> <li>Everything works fine if I remove the prefix. I know that I can set the prefix manually in every migration I run, but well...</li> </ul>
Tags
<php><migration><laravel><laravel-3>
Title
Laravel Migrations - Table Prefix Issue
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USdarksoulsong
UserOwnerUserId
1. USdarksoulsong
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. VO
 singulars
 PostPostId
 POLaravel Migrations - Table Prefix Issue
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POLaravel Migrations - Table Prefix Issue
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTApproveEditSuggestion
CommentsPostId

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.