Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Python SQLAlchemy Basics Introduction to SQLAlchemy Creating a Movie Model

Abigail Solomon
seal-mask
.a{fill-rule:evenodd;}techdegree
Abigail Solomon
Data Analysis Techdegree Student 4,440 Points
Posted by Abigail Solomon
.a{fill-rule:evenodd;}techdegree
Abigail Solomon
Data Analysis Techdegree Student 4,440 Points

Error: Make sure primary_key is spelled correctly and set to True. Unsure about the error in my coding

You can see in my coding that primary_key should be spelled correctly and set to True. I'm not sure why I'm receiving this error and if there's anything I can do to correct my coding.

models.py 
# insert your code here
from sqlalchemy import create_engine, Column, Integer, String 
from sqlalchemy.ext.declarative import declarative_base

engine = create_engine('sqlite:///movies.db', echo=False)

Base = declarative_base()

class Movie(Base):
    __tablename__ = 'movies'

    id = Column(Integer, primary_key = True)
    movie_title = Column(String)
    genre = Column(String)

1 Answer

Travis Alstrand
seal-mask
.a{fill-rule:evenodd;}techdegree seal-36
Travis Alstrand
Treehouse Project Reviewer
Travis Alstrand
.a{fill-rule:evenodd;}techdegree seal-36
Travis Alstrand
Treehouse Project Reviewer

This appears to be something that the Challenge's backend is being a bit too specific on. I tried removing the spaces and I passed

id = Column(Integer, primary_key=True)

I don't believe this would be necessary normally in SQLAlchemy though. I'll make note of this potential issue, thanks for bringing it up!