RDF::Q...::Load(3pm)

πŸ’– NAME πŸ’–

okay bestie, so RDF::Query::Plan::Load</p> is an executable query plan for LOAD operations. that's the whole vibe. it's the lil plan node that actually goes and does the loading. πŸ’…

this page is the RDF::Q...::Load(3pm) manual from the User Contributed Perl Documentation, and yes, the girlies who write Perl docs really did abbreviate it like that. we love a mysterious ellipsis. πŸŽ€


✨ VERSION ✨

this doc describes RDF::Query::Plan::Load version 2.919. no cap, that's the number. note it, screenshot it. 🫢


🌸 METHODS 🌸

first things first, bestie: beyond the methods documented right here below, this class inherits methods from the RDF::Query::Plan class. so there's a whole extra lore drop over there, iykyk. πŸ¦‹

  • new ( $url, $graph )

not gonna lie, they gave us the signature and then... nothing else. that's the whole entry. iconic in a minimalist way, I guess. 😭

  • execute ( $execution_context )

again, just the signature, no gossip attached. it executes, and it takes an $execution_context. that's what we know. πŸ’€

  • next

just the name, bestie. no description came with it. so mysterious of her. πŸ™ˆ

  • close

same deal β€” signature only, zero elaboration. the girls are keeping secrets. πŸ’…

  • url

returns the URL to load data from. simple as that, and honestly? obsessed. ✨

  • namedgraph

returns the optional graph name to load the data with. optional!! she's flexible, she's every-girl. πŸ”₯

  • distinct

returns true if the pattern is guaranteed to return distinct results. so it's a little yes/no vibe check on the pattern's deduplication energy. πŸ’œ

  • ordered

returns true if the pattern is guaranteed to return ordered results. same energy as distinct but make it about order instead of uniqueness. 🌈

  • plan_node_name

returns the string name of this plan node β€” and the reason is very valid: it's suitable for use in serialization. so it's the name that goes on the little name tag when this node gets packed up and shipped out. πŸŽ€

  • plan_prototype

returns a list of scalar identifiers for the type of the content (children) nodes of this plan node. and if you wanna know which identifiers are actually allowed, go check RDF::Query::Plan β€” it's got the full list. ⭐

  • plan_node_data

returns the data for this plan node that corresponds to the values described by the signature returned by plan_prototype. they're matching sets, bestie, that's the whole point. 🧚

  • graph ( $g )

signature only, no description. she said "figure it out." 😭

  • is_update

returns true if the plan represents an update operation. yes, as opposed to a read situation. she knows what she is. πŸ‘‘


πŸ’Œ AUTHOR πŸ’Œ

the one and only Gregory Todd Williams <gwilliams@cpan.org> wrote this. we thank her for her service. 🫢✨


and that's a wrap, bestie! this came from perl v5.40.1, dated 2025-08-18, in the RDF::Q...::Load(3pm) page. go slay your LOAD operations, ok? periodt. πŸ’…πŸ’–πŸŒΈ

πŸ“¦ where this page comes from