Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Ticket #149 (closed defect: fixed)

Opened 14 years ago

Last modified 8 years ago

[PATCH]CatWalk doesn't like custom joins

Reported by: jchu@… Owned by: anonymous
Priority: normal Milestone: 0.9
Component: Toolbox Version: 0.9a6
Severity: normal Keywords:


I've created a new RelatedJoin? subclass called ExtraRelatedJoin?.

The explanation for it is here:  http://xentac.net/~jchu/blog/technology/sqlobject-extra-relatedjoins.html

It does act differently from a regular RelatedJoin?. I realize that CatWalk doesn't have to support these sorts of things, but could we get something to get CatWalk to not barf when we use them?

Maybe a way to enable and disable column displays?


catwalk.patch Download (509 bytes) - added by anonymous 13 years ago.
string comp replaced by generic regexp in catwalk.renderFormColumn

Change History

comment:1 Changed 14 years ago by Ronald Jaramillo

  • Milestone set to 0.9

Generally speaking, CatWalk should ignore 'unrecognizable' columns, and allow some sort of delegation.

Changed 13 years ago by anonymous

string comp replaced by generic regexp in catwalk.renderFormColumn

comment:2 Changed 13 years ago by joost

  • Summary changed from CatWalk doesn't like custom joins to [PATCH]CatWalk doesn't like custom joins

The patch filters all SO*Join columns in the add/edit panel instead of just the 3 standard ones. This way you can atleast add/edit objects with ExtraRelatedJoins?. Ofcourse there is still the issue of how to display this type of column in browse view. By default its value is assigned trough:

value = '%s'% getattr(row,columncolumnName?)

What are youre thoughts on delegation Ronald?

comment:3 Changed 13 years ago by anonymous

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.