Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="javapadawan" data-source="post: 1120644" data-attributes="member: 1444">True. That was originally how I did things with the old database, by having a validation table of sorts for combo box options on create and search. It is pretty unlikely that anyone would want/need to add or modify spell schools... so it's probably a safe bet to move school out of attribute and back into the spell table.Good point. If I was going to be doing a spell sort based on level, it would probably be something like, where attribute_type_id = [class] and attribute_id = [cleric] order by value. Then the data doesn't necessarily even need to be converted.But in your example, I need to check for spells whose levels fall within a certain range. I could still say where attribute_type_id = [class] to avoid an attempt to parse "a pinch of wool" to an integer, however, that still leaves me with my numbers as strings. Same goes for if I want to try to calculate how many pages a spellbook with a given list of spells uses up.I generally use SQL in Java to query the database, even though it's that nasty JetSQL Access uses. Oracle PL/SQL gives me a nice TO_NUMBER function I can fall back on, but I don't know if JetSQL offers anything similar. If not, or if their version is too time-intensive, we might well be better off having a note field or something similar to store non-numeric data, and keep our value field pure. <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=":)" />Indeed. MUCH more fun than actually working. <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=":)" /></blockquote>

Verification