Library sample data changes

7 views
Skip to first unread message

Sean Colsen

unread,
Mar 6, 2025, 9:10:01 AMMar 6
to Mathesar Developers

Team,

I brought this up during yesterday’s meeting, but I wanted to circle back and try to push it forward: I would like to make some changes to our library sample data.

I see these changes as important for our “Table Query Integration” project, so I’d like to invest a modicum of time into improving the sample data because I think it will help with design.

Process-wise, I’d like to take this opportunity to invite others to suggest (small) changes to the library sample data. Then I’d like make sure we’re all in agreement about the changes to make. Once we have agreement on the changes to make, then we can figure out who will do it. I’ll do it if necessary.

Here are the changes I want:

  • Add FK from "Books"."Media" to "Media".id.

  • Change all schema, table, and column names to snake_case.

    Why? Because it will make it a bit easier/simpler for us to write SQL against this data. Now we have other sample data sets that demonstrate pretty, Title Case names for users. I find the library data to be incredibly useful for us, internally, and I want to optimize for that. I think snake_case names will make prototyping and discussion easier.

  • Add genres:

    • A genres table with id and name columns.
    • A books_genres table with id, book, and genre columns.
    • Some data in both tables such that all books have at least one genre and some books have several genres.
    • I would want the genres to be flat and simple. I.e. “Fantasy” instead of “Fiction > Fantasy”.

Are there any other changes you want?

Are you okay with the changes I want?

Zack Krida

unread,
Mar 7, 2025, 2:57:12 PMMar 7
to Sean Colsen, Mathesar Developers
No strong feelings here, I'm fine with your proposed changes and have no further changes.
Reply all
Reply to author
Forward
0 new messages