Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
In WOLips, we can say that a .wod key path is "valid" by adding a "// VALID" to it. You can do this for inline bindings as well.
Is there a similar mechanism in EntityModeler?
I added a "read only" attribute with a "read formatter" (using %P) to transform a VARCHAR into an INTEGER. That way I can create SQL easily to validate and search for values. Really the column should be an INTEGER but it is legacy and I can't change it. This seemed like a reasonable decision.
Back in the old days, Apple's EOModeler never complained about this practice. Our new WOnder EntityModeler gives me warnings every time I save saying essentially that two attributes are referencing the same column. It's a bit annoying. It's a warning so I can ignore it but just wondering if there was some way to flag it as valid.
AARON ROSENZWEIG / Chat 'n Bike
e: aaron@... t: (301) 956-2319