Parse:...ite3fk(3pm)

💖 NAME 💖

Parse::Dia::SQL::Output::SQLite3fk — bestie, this one makes SQL for SQLite version 3, and yes, it comes with foreign key support. Obsessed. 🎀

(It's a User Contributed Perl Documentation page, iykyk.)

---

✨ SYNOPSIS ✨

use Parse::Dia::SQL;
my $dia = Parse::Dia::SQL->new(file => 'foo.dia', db => 'sqlite3fk');
print $dia->get_sql();

Like, that's it. Three lines and you're serving SQL. 💅

---

🌸 DESCRIPTION 🌸

Okay so this little sub-class is the one that creates SQL for the SQLite database version 3. That's the whole vibe. She's a sub-class, she's a specialist, she does one thing and she does it gorgeously. 🦋

🫶 new 🫶

The constructor. That's the girl that starts everything. 💖

Real talk though: object names in SQLite have no inherent limit. So like, 60 has been arbitrarily chosen. Not a rule, just a vibe. A number somebody picked. 🍓

💅 _get_create_table_sql 💅

Generates the create table statement for a single table using SQLite syntax. Let's break down the slay:

• Includes class comments before the table definition. Cute little preface, we love.
• Includes autoupdate triggers based on the class comment. Yes bestie, the comments do WORK around here.
• Includes foreign key support of the form:

foreign key(thisColumn)  references thatTable(thatColumn) {action}

Where {action} is the optional constraint condition, such as 'on delete cascade', exactly as entered in the diagram. No rewriting, no reformatting, no editorializing. What you drew is what you get. ✨

🌈 autoupdate triggers 🌈

If the class comment includes a line like:

<autoupdate:foo/>

Then an 'after update' trigger is generated for this table which executes the statement foo for the updated row. Main character behaviour, honestly. 👑

Examples of use include tracking record modification dates, like this:

"<autoupdate:dtModified=datetime('now')/>"

...or deriving a value from another field, like this:

"<autoupdate:sSoundex=soundex(sName)/>"

Both iconic. Both doing the absolute most for you. 💜

🎀 _create_pk_string 🎀

Overrides the default function to include foreign key clauses. She's not like the other functions. 🫶

⭐ get_schema_drop ⭐

Generates drop table statements for all tables using SQLite syntax:

drop table {foo} if exists

Bye tables, hope you had a nice time. 👋

🦋 get_view_drop 🦋

Generates drop view statements for all tables using SQLite syntax:

drop view {foo} if exists

Same energy, different object. Views said goodbye too. 🌸

💀 _get_fk_drop 💀

Foreign key enforcement is embedded in the table definitions for SQLite, so no output is required here. Nothing to do. Empty. A void. She simply doesn't speak. 😭

🌈 _get_drop_index_sql 🌈

Drop index statement, using SQLite syntax:

drop index {foo} if exists

🧚 get_permissions_create 🧚

SQLite doesn't support permissions, so this output is suppressed. Not us being quiet — SQLite just doesn't do that. Periodt. 💅

🧚 get_permissions_drop 🧚

SQLite doesn't support permissions, so this output is suppressed. Same deal, bestie. Nothing to see. 💖

🍓 _get_create_association_sql 🍓

Foreign key enforcement is embedded in the table definitions for SQLite, so no output is required here. Again! Because the keys already live inside the table defs. She's efficient like that. ✨

---

👑 TODO 👑

Things that might get added in future versions. The pipeline. The vision board. 🎀

💜 Views 💜

Views haven't been tested. They might already work, but who knows... 🤷‍♀️ Not me. Not her. Nobody. It's giving mystery.

💜 Other stuff 💜

Bugs etc. Vague! Iconic! Unspecified! 💀

---

That's the whole page, bestie. This lil' gem ships with perl v5.36.0 and was dated 2022-11-19. Go make some tables with foreign keys, you absolute legend. 🫶✨💖