StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17198089
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-06-19T17:58:45.113
FavoriteCount
0
LastActivityDate
2013-06-19T18:35:33.220
LastEditDate
2013-06-19T18:35:33.220
LastEditorUserId
172106
OwnerUserId
172106
ParentId
17178497
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
I see that <code>rspec-rails/lib/rspec/rails/tasks/rspec.rake</code> defines this for the <code>spec</code> task: <pre><code>spec_prereq = Rails.configuration.generators.options[:rails][:orm] == :active_record ? "test:prepare" : :noop task :noop do; end task :default => :spec # other stuff desc "Run all specs in spec directory (excluding plugin specs)" RSpec::Core::RakeTask.new(:spec => spec_prereq) </code></pre> ...which runs: <ul> <li><code>db:load_config</code></li> <li><code>db:test:purge</code></li> <li><code>db:test:load</code></li> <li><code>db:test:load_schema</code></li> <li><code>db:schema:load</code></li> </ul> I see that, when running <code>rake db:schema:load</code>, I get: <pre><code>-- enable_extension("plpgsql") -> 0.0161s -- enable_extension("uuid-ossp") -> 0.0063s -- create_table("growers", {:id=>false, :force=>true}) -> 0.0049s -- initialize_schema_migrations_table() -> 0.0062s </code></pre> ...which is different than when I run the migration: <pre><code>== CreateGrowers: migrating ================================================== -- enable_extension("uuid-ossp") -> 0.0050s -- create_table(:growers, {:id=>:uuid}) -> 0.0052s == CreateGrowers: migrated (0.0103s) ========================================= </code></pre> Thus, it seems to me that the <code>db:schema:load</code> task isn't creating the table with the UUID primary key, thus causing the failures. Seems like a Rails bug?? Update: I guess I'll find out if it's a Rails bug: <a href="https://github.com/rails/rails/issues/11016" rel="nofollow">Issue 11016</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORSpec, Rails 4, Postgres, UUID primary keys: id is null with Rake + RSpec, but is fine in RSpec or console
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USturboladen
UserOwnerUserId
1. USturboladen
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORSpec, Rails 4, Postgres, UUID primary keys: id is null with Rake + RSpec, but is fine in RSpec or console
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COLooks like they'll be fixing it in Rails 4.0.1. They should name the release after you.
 singulars
 PostPostId
 PO
 UserUserId
 USyuяi

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.