6
Caprico
4y

I laughed so hard when I saw this method for laravel 5.3. Why does this exist!!! πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚

Comments
  • 2
    You certainly know nothing about Laravel then.
  • 1
    πŸ‘πŸΌπŸ‘πŸΌπŸ‘πŸΌπŸ‘πŸΌπŸ‘πŸΌπŸ‘πŸΌπŸ‘πŸΌπŸ‘πŸΌπŸ‘πŸΌπŸ‘πŸΌπŸ‘πŸΌπŸ‘πŸΌπŸ‘πŸΌπŸ‘πŸΌ
  • 1
    @jirehstudios I've only been working in it for about 3 months so I'm still learning. But. Savage man. Savage
  • 1
    No I have knowledge and have built migrations. my question was more of why does this method exist. And as @chasb96 explained it I understand why and how it's used.
  • 2
    It's also useful for doing bulk inserts (1+ million records) where foreign key constraint checking can slow things down.
  • 1
    @jirehstudios let's not get too stack overflowy in here πŸ˜‚
  • 0
    Yeah disableing foreign keys for a period of time (for migration or huge bulk inserts) will save you alot of headaches. Most databases allow alter statements to disable keys for it makes sense for your framework to simple provide a wrapper to provide the same functionality. When I'm building a wrapper around something, I also try to preserve and expose as much of the functionality as possible.
Add Comment