I've noticed the manager templates make some assumptions about the names of the relations and fields mapped on the relations. For example, I have a Customer and Address table (1 to m). The name of the field mapped on the relation is 'Addresses'. It seems this breaks the code, since the table name is Address and the field name is Addresses. Is there anyway to account for this in the templates? If it's not possible, thats fine. I just do not know enough about the templates and generation process.

Thanks

Whoah. I haven't been around here in awhile and I'm stoked that people are still interested

So anyway....

If you're running into troubles with the templates and relation names, check the corresponding place in the templates for relation.UtilizingPropertyName. If it's not that, it's a bug in the template. Which is entirely possible. These templates were written over the course of a week or two.

Altough I've been using them for every project since, there is no way we got all the bugs out of them.

If you fix a bug, please submit the patch to the subversion repo. If you don't have access, ask Otis.

cmartinbot wrote:

Whoah. I haven't been around here in awhile and I'm stoked that people are still interested

Dude, these are in heavy usage now in two of my client sites. They rock. I've spent many hours back-coding these into older projects. Sweetness! Keep at them!

swallace wrote:

cmartinbot wrote:

Whoah. I haven't been around here in awhile and I'm stoked that people are still interested

Dude, these are in heavy usage now in two of my client sites. They rock. I've spent many hours back-coding these into older projects. Sweetness! Keep at them!

Have you ran into any trouble with changing the mapped on field relation names?

No, in both instances I had created the relations in Designer and given them names myself. I think we're talking about the same thing.