Re: Using AI Tools to Generate Dynamic Text for MySQL Applications

[Herrick Peterson]

Hello David

One thing I would add on top of what Ammara said: think about caching and versioning too, not just schema shape. AI-generated text isn't free to regenerate, so if you're calling an API each time for headings/product names, add a content_hash or prompt_hash column so you can check "have I already generated this exact thing" before firing off another API call. Saves cost and keeps things consistent if the same prompt somehow runs twice.

Also worth adding a status or is_approved column on content_items if there's any chance a human reviews AI output before it goes live, AI-generated product names/headings can occasionally produce something you don't want published as-is, so having a review gate baked into the schema (rather than bolting it on later) saves a headache.

For the style table, JSON column instead of rigid columns (font_family, font_weight etc) can be worth considering too if you expect the style properties to grow or vary a lot, MySQL's JSON functions are solid enough now for querying into it when needed, though a separate table like Ammara's is definitely cleaner if your style attributes are fixed and known upfront.

Regards,
Herrick
DevOps Engineer
Accuweb,cloud