Why did the Tabla class get split into type families?

[expipiplus1]

This seems to have changed in commit 630c6bd: changed api a lot

One advantage of the class representation is that sensible defaults can be given for fields such as SchemaName.

A slightly related issue: #12

[k0001]

Yeah, that commit reorganized much stuff. Mostly just a general cleanup.

In practice, I don't think there's much difference between the standalone type families vs. the typeclass and associated types approach in this case. I tried both, and the current one seemed a bit cleaner.

That thing you mention about things like SchemaName having a default is a minor but interesting point. I actually don't like the idea of providing a default here. With tisch, I'm trying to make it as hard as possible to shot yourself in the foot, and being explicit about things is a good way to achieve that. Granted, having a default schema name is not a big deal, but still I'd prefer people to understand where their tables are found so that they can better relate to the generated SQL, error messages, and such.

[expipiplus1]

That's understandable regarding defaults.

One nice thing about doing this in a class is that there's one central place for the user to see what they need to define for their table to work.

If you say that it's cleaner this way I'm happy :)