Information générale
Catégorie:
The Mere Mortals .NET Framework
Thanks for taking care of it in the next version. I was afraid there was no elegant solution. I subclassed mmType and did a blanket replace in the data objects. That will hold me for now.
While we're looking at future features, how about...
- When creating data objects, how about a global "Use all defaults" button to select all defaults. If I'm bringing in a lot of defaults, it would be easier to go through and un-select rather than deal with every one.
- For SQL, the Bit type is used for a boolean field. It sure would be nice if MM would take care of that interpetation (0 = false, 1 = true) for me. But maybe that's just me being lazy :)
- For some reason (I'm sure this isn't a feature) when I generate Data Objects (Microsoft SQL), my tables are listed in some odd order in the list. Alphabetical (or an option for it) would be nice.
- Some sort of option for mmType.IsEmpty() that would just check for nulls (or an alternate IsNull()). Most of the time when I say a field is required, I don't mean it has to be true (boolean), non-zero (numeric) or non-zero length string (string). If it is, I think it's something I probably need to add to the rules.
There has been a lot to learn, but the more I use MM, the more I like it.
Jeff
Précédent
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement