In its current state, the generated Photon is differently generated for various database providers. However, a use case can be to use sqlite locally at the inception of a project (for ease of on-boarding amongst other reasons) but move to a DB capable of more heavy lifting.

This issue persist thoughts around this feature.

Here is a note from a user:

For right now today I can use the same DB everywhere, but once everything is getting closer to being production-ready I think allowing for multiple providers is a huge help for new devs learning the framework—they can use sqlite locally and get started without worrying about installing/configuring MySQL or Postgres, everything “just works”. This is the approach that Rails kind of pioneered and it’s been great. I almost always start with sqlite locally and only go to MySQL if/when I end up needing to write some MySQL-specific SQL that sqlite doesn’t support