Pinto:...tration(3pm)

📦
version 0.14000 · 7 versions
, in debian trixie, ubuntu resolute

💖 NAME 💖

Pinto::Schema::Result::Registration — bestie, this is literally the class that represents the relationship between a Package and a Stack. That's the whole vibe. It's a join-table baddie. 💅

✨ VERSION ✨

version 0.14 — yes she's on 0.14, she's been through some things, she's thriving. 🦋

🎀 NAME (again, but make it official) 🎀

Pinto::Schema::Result::Registration

okay so the manpage really does say NAME twice. Not a typo on my part, not me being extra (for once). It's giving "she introduced herself, then introduced herself again with her full government name." iconic. 👑

🗄️ TABLE: "registration" 🗄️

That's the table she lives in. One table. Her whole world. 🌸

💅 ACCESSORS 💅

these are her columns, her little properties, her whole personality. one bullet-point per attribute, all facts preserved, no notes:

🆔 id

data_type: 'integer'
is_auto_increment: 1
is_nullable: 0

an integer, auto-incrementing, and it is not nullable. so you can't leave her on read, okay? 😭

🔁 revision

data_type: 'integer'
is_foreign_key: 1
is_nullable: 0

an integer, it's a foreign key, and nope, not nullable. she points at something else and she's committed to it. 🫶

📦 package_name

data_type: 'text'
is_nullable: 0

text, not nullable. that's it, that's the whole description. straightforward queen. ✨

📦 package

data_type: 'integer'
is_foreign_key: 1
is_nullable: 0

integer, foreign key, not nullable. yes there's both package_name and package, no I'm not going to explain why, the manpage doesn't, and I don't make the rules. 💀

🗂️ distribution

data_type: 'integer'
is_foreign_key: 1
is_nullable: 0

integer, foreign key, not nullable. another pointer, another bestie she's holding hands with. 💜

📌 is_pinned

data_type: 'boolean'
is_nullable: 0

boolean, not nullable. so it's true or it's false, there is no "u up?" in between. periodt. 🎀

👑 PRIMARY KEY 👑

  • "id"

that's it. one primary key, she's decisive, she knows what she wants. slay. 💖

🌈 UNIQUE CONSTRAINTS 🌈

"revision_package_name_unique"

  • "revision"
  • "package_name"

so that combo is unique — you can't have the same revision and package_name pairing twice. the database said "we're not doing duplicates today bestie" and honestly? correct. 🔥

🦋 RELATIONS 🦋

these are her committed relationships (in the database sense, obviously). all three are belongs_to, she's not out here being messy:

distribution

  • Type: belongs_to
  • Related object: Pinto::Schema::Result::Distribution

package

  • Type: belongs_to
  • Related object: Pinto::Schema::Result::Package

revision

  • Type: belongs_to
  • Related object: Pinto::Schema::Result::Revision

look at her. three belongs_tos, zero has_manys. she's the one who shows up, she's not the one who texts first. 💅

🧚 Moose ROLES APPLIED 🧚

  • Pinto::Role::Schema::Result

just the one role, and she wears it beautifully. 🎀

✍️ AUTHOR ✍️

Jeffrey Ryan Thalhammer <jeff@stratopan.com>

the icon who made her. we stan. 🌸

This software is copyright (c) 2015 by Jeffrey Ryan Thalhammer.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.

okay so lowkey important: same terms as the Perl 5 programming language system itself. that's the license. don't be weird about it, bestie. 🫶

and that's the whole page, no cap. this was Pinto:...tration(3pm) from the perl v5.40.1 crew, dated 2025-04-21. mwah, go build something cute with it. 💖✨🎀

📦 where this page comes from