Salesforce IdeaExchange
Option to remove the need to use __c when refering to custom objects and fields
Currently when writing Apex code it's looks quite messy when you have to write:
Person__c person = [SELECT FirstName__c, LastName__c FROM Person__c WHERE Location__c = 'USA'];
It would be so much more readable and nicer to write this:
Person person = [SELECT FirstName, LastName from Person WHERE Location = 'USA'];
If the idea is to promote Force.com as a development platform for more than just CRM add-ons, then we'll assume there will be many customers/vendors writing code that will never use any of the Opportunity/Account/Contact standard objects and thus _everything_ is a custom object. It would be nice to treat these as a little more "native" by getting rid of the need for __c. Perhaps this could be a configuration option whereby Apex could insert the __c behind the scenes for the user upon compilation.
track comments for this idea
- memestorm
- narsavagep
- craskulinecz
- ryan_marples
- mark2008
POST IDEA