Alzabo::MySQL(3pm)

📦
version 0.92 · 2 versions
  • 0.92 · debian bookworm, debian trixie, ubuntu noble, ubuntu resolute, ubuntu stonking (latest)
  • 0.92 · ubuntu jammy
, in debian bookworm, debian trixie, ubuntu noble, ubuntu resolute, ubuntu stonking

💖 NAME 💖

Alzabo::MySQL — it's giving "Alzabo and MySQL", bestie. That's the whole vibe. ✨

🌸 DESCRIPTION 🌸

okay so this whole page is about the special support Alzabo has for MySQL, and honestly also the stuff it just... doesn't do. We keep it real here. 🫶

The MySQL support is based on the 3.23. release series, with a lil bit of support for features that are starting to show up in the 4.0. releases. Earlier versions of MySQL will probably work with Alzabo, but no cap — Alzabo cannot magically make those releases support new features like fulltext indexes. The magic has limits, bestie. 💅

👑 Indexes 👑

  • Alzabo supports the ability to specify prefixes when adding an index. And like, prefixes are required when you're attempting to index any sort of text or blob column. Not optional. Required required. 🔥
  • Alzabo also supports the creation of fulltext indexes and their use in SELECT and WHERE clauses. This includes the ability to get back the score given for a match as part of a select, using the "function" or "select" methods of either table or schema objects. Obsessed, actually. ✨

🦋 Reverse Engineering 🦋

  • When reverse engineering a schema, Alzabo knows that MySQL has "default defaults" for certain column types. For example, if a DATE column is specified as NOT NULL but is not assigned a default, MySQL gives this column a default of '0000-00-00'.

Because Alzabo knows about this, it will ignore these defaults when reverse engineering an RDBMS. It's called ✨awareness✨.

  • Similarly, Alzabo knows that MySQL assigns default "lengths" to many column types. For example, if given INTEGER as a column type, MySQL will convert this to INTEGER(11) or INTEGER(10), depending on the version of MySQL being used.

Again, Alzabo ignores these lengths when reverse engineering a schema. Not it pretending they're not there — it literally ignores them. 🙈

  • All of this may lead to apparent inconsistencies when using the with the Alzabo::Create::Schema->sync_backend or Alzabo::Create::Schema->sync_backend_sql methods. If you are using this feature from the web based schema creator, you will see that even immediately after running the sync_backend() method, Alzabo may still think there are differences between the two schemas.
This is not a problem, bestie!! 😭 Running the SQL Alzabo generates will not actually change your database. Vibe check passed. 💖

🎀 Transactions 🎀

Alzabo will try to use transactions whenever appropriate. Unfortunately, there is no way to determine whether or not a given table supports transactions, so Alzabo simply calls DBI's begin_work() method, whether or not this will actually do anything. It's giving "shooting your shot". 🏹

💜 Constraints and Foreign Keys 💜

  • Column constraints are treated as column attributes.
  • Foreign key constraints are not generated when generating SQL for a MySQL schema. This will probably change in the future, but for now? Nope. Not today. 💀

🌈 Table Types 🌈

These can be specified as a table attribute. That's it, that's the section. Short and iconic. 👑

perl v5.34.0 · 2022-06-14 — okay that's the whole page bestie, mwah 💋 thanks for reading, go forth and slay your schema, iykyk 🧚✨💖

📦 where this page comes from