And I see many of the attributes I can include in a query there. So when a query is run, this class is generated, which populates itself with the relevant data from the database, then the query selects the necessary data from this on-the-fly generated class. Does that seem right?
Since there is no inner or outter join specified, inner join is obviously being used where 'join' is specified (outter join having to be explicitly defined where an outter join is needed). How come you explicitly specify 'inner join' at the bottom when you could just use 'join' again as your inner join?
Obviously join and inner join accomplish the same thing, just curious why one is not explicitly defined and the other is.
I expanded on something done by someone from the osTicket team. it was some weird stylistic choice that they made and I just followed.