Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 370727
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T14:02:45+00:00 2026-05-12T14:02:45+00:00

I’m new to CakePHP, and I’m trying to decide between the schema shell that

  • 0

I’m new to CakePHP, and I’m trying to decide between the schema shell that comes with CakePHP and the migrations tools that were written by Joel Moss and Georgi Momchilov.

So far I haven’t found any direct support in either of them for creating foreign key constraints. It appears that you might be able to write raw SQL in a migration to create a foreign key.

Have I missed something? Is there support somewhere? Should I even be using foreign keys? I’ve seen a few comments related to CakePHP or Ruby on Rails saying that foreign key constraints are discouraged. Our database is only used by one application.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-12T14:02:46+00:00Added an answer on May 12, 2026 at 2:02 pm

    I wouldn’t say that they’re discouraged, per se. With both CakePHP and Rails, the data integrity that foreign keys offer is handled by the framework. That said, it’s only true if you do everything the “right” way. If you’re writing your own SQL, operating in a non-standard manner or accessing/manipulating the data through any other means, then foreign keys are definitely a good idea, in my opinion.

    I’ve never used migration tools for CakePHP, but in my limited Rails work, I’ve always applied the keys in the migration using SQL. That way you get all of the inherent benefits of both. You have your migration and you get your domain constraints in case you ever skirt the framework to achieve some particular result.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.