Thanks Jweltzer,

So It means I need to have account field named  name in the visual force page to use it any where in the class.So in order to use name field in the getter method I need to have it in the visual force page.Is that correct.?

I am not clear about the explanation on the populated field.

Did  u mean that as soon as the visual force page is loaded, the fields on the page are  populated with the values from the database and then constructor gets fired which retrieves the name field value through the getrecord()  method and then we can use it in the getter method .Am I correct on that.I really need to understand this correctly to write programs properly.

I appreciate you for enhancing my knowledge

Thanks,

Trick 

Yes you are correct, you need to have the field on your page if you want to use it in your class.

This doesn't really have much to do with your constructor.  When you use a standardController, right when you request the page, we generate a SOQL query that is made up of only the fields that are on your page, and we execute that query and hold on to the record that's returned by that query.

Your extension is calling the standardController's getRecord() method in the constructor, so what it's getting is the record from the result of that initial query.  This means that you only have access to the fields that are on your page, because that's all that is in the constructed SOQL query.  So if you want to use a field anywhere in your extension (doesn't matter if it's a getter or an action method or anything else), you must either have that field somewhere on your page so that it gets queried for on initial page load, or you need to execute your own separate query for the record somewhere in your extension, and use that record instead of the one you are getting from the standardController.

I think I got your point.Let me see if I am correct. As soon as the page is loaded,standard controller executes a default getter method(which in our case would be account getter method) which queries the fields on the page and returns a result.The constructor of the extension class is responsible for getting the record from the initial query through GetRecord() method of the standard controller and then we can access any of the field names which are a part of the query anywhere in the extension class..

Whether I am right or wrong I am going to disturb you any further because you have already explained a lot.

Thanks,

Trick

There is no "default getter method".  The standard controller simply executes a query and stores off the result right when the page is requested.

The extension class can call the getRecord() method whenever, doesn't have to be in the constructor, although the constructor is the only point that you actually have access to the standardController object, so yes that's generally when people will call the getRecord() method and store it off in the extension class.

Other than that it sounds like you've got it.

Every standard controller includes a getter method that returns the record specified by the id query string parameter in the page URL. This method allows the associated page markup to reference fields on the context record by using {!object} syntax, where object is the lowercase name of the object associated with the controller. For example, a page that uses the Account standard controller can use {!account.name} to return the value of the name

 field on the account that is currently in context.

I have taken the above lines from the help section on the standard controller account.If you carefully read first line given above, you will understand what I am trying to say.

Every standard controller includes a getter method that returns the record specified by the id

query string parameter in the page URL.

This means that internally system executes getter method which returns a result through queries.I will look for more info on this if I get more info I will come back to you.

Thanks Trick

This was possible because the Account standard controller includes a getter method named getAccount

 that returns the specified account record. We can mimic this functionality in a custom controller with the following code:-

In the below given code they have actually used standardcontroller method getaccount()(which I called a default getter method in our example).They are actually showing how the standardcontroller getccount() method queries the fields on our page before returning the result.

I hope what I am saying makes some sense.

Thanks,

Trick

    public String getName() {
        return 'MyController';
    }

    public Account getAccount() {
        return [select id, name from Account 
                 where id = :ApexPages.currentPage().getParameters().get('id')]; 
    } 
}