Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
White Dwarf Reflections
Columns
Weekly Digests
Weekly News Digest
Freebies, Sales & Bundles
RPG Print News
RPG Crowdfunding News
Game Content
ENterplanetary DimENsions
Mythological Figures
Opinion
Worlds of Design
Peregrine's Nest
RPG Evolution
Other Columns
From the Freelancing Frontline
Monster ENcyclopedia
WotC/TSR Alumni Look Back
4 Hours w/RSD (Ryan Dancey)
The Road to 3E (Jonathan Tweet)
Greenwood's Realms (Ed Greenwood)
Drawmij's TSR (Jim Ward)
Community
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Resources
Wiki
Pages
Latest activity
Media
New media
New comments
Search media
Downloads
Latest reviews
Search resources
EN Publishing
Store
EN5ider
Adventures in ZEITGEIST
Awfully Cheerful Engine
What's OLD is NEW
Judge Dredd & The Worlds Of 2000AD
War of the Burning Sky
Level Up: Advanced 5E
Events & Releases
Upcoming Events
Private Events
Featured Events
Socials!
EN Publishing
Twitter
BlueSky
Facebook
Instagram
EN World
BlueSky
YouTube
Facebook
Twitter
Twitch
Podcast
Features
Top 5 RPGs Compiled Charts 2004-Present
Adventure Game Industry Market Research Summary (RPGs) V1.0
Ryan Dancey: Acquiring TSR
Q&A With Gary Gygax
D&D Rules FAQs
TSR, WotC, & Paizo: A Comparative History
D&D Pronunciation Guide
Million Dollar TTRPG Kickstarters
Tabletop RPG Podcast Hall of Fame
Eric Noah's Unofficial D&D 3rd Edition News
D&D in the Mainstream
D&D & RPG History
About Morrus
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Upgrade your account to a Community Supporter account and remove most of the site ads.
Community
General Tabletop Discussion
*Geek Talk & Media
SRD Spells Database 3.5
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="javapadawan" data-source="post: 1135497" data-attributes="member: 1444"><p>I agree. And in that case, it does seem as though it would be best to keep School as an attribute.</p><p></p><p>I think an errata field is a good idea. In addition to a date field though, it might also be helpful to have a source field. This way you'd know that a particular piece of errata came from Sage Advice, from an official WotC errata document, from a reprinting of the spell in a later sourcebook, etc. </p><p></p><p>It would be easy enough to add these fields to the spell table, though as you mentioned, if a spell was errata'd more than once you'd lose the original record of that... unless errata was stored in another table. (For someone who dislikes adding extra tables, I sure seem to be suggesting a lot of them, don't I? <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f609.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=";)" title="Wink ;)" data-smilie="2"data-shortname=";)" /> ) </p><p></p><p>What if you had something like this:</p><p></p><p>spell_has_errata</p><p>----------------</p><p>spell_has_errata_id (AutoNumber)</p><p>spell_id (Number, foreign key : spell)</p><p>errata (Memo)</p><p>source (Text)</p><p>date (Date or Text, text could allow an exact date or a general date, like 5/05/2003 vs. 5/2003)</p><p></p><p>The drawback of this is that we'd need to do an outer join to pull back both spells that have errata and those that don't, but the upside is that no matter how many times a spell is errata'd, we would have access to not only the original text of the spell but also each subsequent change. Additionally, there may be those who don't like the errata and would rather use a spell as originally written, or might just be curious as to how much has changed over the course of a spell's life. </p><p></p><p>Overkill? Heh, maybe. But all this could be transparent to the end user. When printing out the spell description for viewing, we could just append the errata to the end of the long description, prefixed by the source and date, looking something like this:</p><p></p><p>...</p><p>This spell does blah blah blah to all creatures within a fifty foot radius.</p><p></p><p>ERRATA: Sage Advice, May 2003</p><p>This spell does blah blah blah to all living creatures within a fifty foot radius.</p><p></p><p>ERRATA: PHB v3.5 Official Errata, July 15, 2003</p><p>This spell does blah blah blah to all living creatures within a sixty foot radius.</p><p>...</p><p></p><p></p><p></p><p></p><p>To paraphrase a popular commercial series...</p><p></p><p>Adding a Verified checkbox to the spell table: Good idea.</p><p></p><p>Adding a Verified date field to the spell table: Great idea.</p><p></p><p>Getting your players to do the work for you: Priceless. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile :)" data-smilie="1"data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="javapadawan, post: 1135497, member: 1444"] I agree. And in that case, it does seem as though it would be best to keep School as an attribute. I think an errata field is a good idea. In addition to a date field though, it might also be helpful to have a source field. This way you'd know that a particular piece of errata came from Sage Advice, from an official WotC errata document, from a reprinting of the spell in a later sourcebook, etc. It would be easy enough to add these fields to the spell table, though as you mentioned, if a spell was errata'd more than once you'd lose the original record of that... unless errata was stored in another table. (For someone who dislikes adding extra tables, I sure seem to be suggesting a lot of them, don't I? ;) ) What if you had something like this: spell_has_errata ---------------- spell_has_errata_id (AutoNumber) spell_id (Number, foreign key : spell) errata (Memo) source (Text) date (Date or Text, text could allow an exact date or a general date, like 5/05/2003 vs. 5/2003) The drawback of this is that we'd need to do an outer join to pull back both spells that have errata and those that don't, but the upside is that no matter how many times a spell is errata'd, we would have access to not only the original text of the spell but also each subsequent change. Additionally, there may be those who don't like the errata and would rather use a spell as originally written, or might just be curious as to how much has changed over the course of a spell's life. Overkill? Heh, maybe. But all this could be transparent to the end user. When printing out the spell description for viewing, we could just append the errata to the end of the long description, prefixed by the source and date, looking something like this: ... This spell does blah blah blah to all creatures within a fifty foot radius. ERRATA: Sage Advice, May 2003 This spell does blah blah blah to all living creatures within a fifty foot radius. ERRATA: PHB v3.5 Official Errata, July 15, 2003 This spell does blah blah blah to all living creatures within a sixty foot radius. ... To paraphrase a popular commercial series... Adding a Verified checkbox to the spell table: Good idea. Adding a Verified date field to the spell table: Great idea. Getting your players to do the work for you: Priceless. :) [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Geek Talk & Media
SRD Spells Database 3.5
Top