DMZ 1.7.1 (DataMapper OverZealous Edition)

[eluser]OverZealous[/eluser]
@BRK Network
I don't think you are going to be able to use that kind of naming scheme with DMZ. It's probably going to give you a lot of trouble. Besides that, it sounds like you are over-complicating it.

Note, DMZ does not have any built-in method for dealing with joins between more than 2 classes. You must have a model in the middle if you want to connect more than 2. There's a note about that on the troubleshooting page.

Think about your information as objects first. Don't worry so much about the database, since DMZ works backwards from the objects. You are trying to represent something (and I don't completely understand what), but it looks very simple:

Users have multiple Lessons.
A Lesson has a price, a school, and maybe some other information.
etc.

If you instead focus on the objects and how they relate, the database is much easier to build based on the models. The database built on DMZ rules tends to describe the models and relationships very well.

This is the one major drawback to even a very fast ORM like DMZ: you are going to have to design your application and database around the framework, not the other way around. Some ORMs provide a lot more customization, but that comes at the expense of simplicity and performance.