I woud solve this like problem this:

https://play.golang.org/p/gCwlNRZlR47

package main

import (
	"fmt"
	"time"
)


//Model is associated with the database
type Model struct {
	ID        string     
	CreatedAt time.Time 
	UpdatedAt time.Time
	DeletedAt *time.Time
	Version   int
}

type ModelModeler struct {  
	Model	
}

func (m ModelModeler) ID() string {
	return m.Model.ID
}

func (m ModelModeler) Version() int {
	return m.Model.Version
}

func (m ModelModeler) SetID(s string) {
	m.Model.ID = s
}

func (m ModelModeler) SetVersion(i int) {
	m.Model.Version = i
}

type Modeler interface{
        ID() string
	SetID(string)
	Version() int
	SetVersion(int)
}

func SomeFunctionUseModeler(m Modeler) {
  	fmt.Printf("Model: %s %d\n", m.ID(), m.Version())
}

func main() {
	m := ModelModeler{ Model: Model{ "Z80", time.Now(), time.Now(), nil, 1}}
	SomeFunctionUseModeler(m) 
}

If you find it a lot of work to write the ModelModeler struct and methods, it's quite easy to write a code generator with 'go/ast' and go generate that will do it for you.

I'm not sure, but I think you are suggesting that if a struct field is named F with type T, then it should automatically satisfy an interface with a method F() T. If you want to write that up as a language change proposal, please see https://golang.org/s/proposal. But I don't think such a change is particularly likely to be accepted. Any type can have methods, so why should struct types be special in this way? Also, in general interfaces describe behavior, but a field is just data. And, of course, people will immediately want some way to change the field, not just fetch it.

I'm going to close this issue, but please feel free to open a language change proposal.

If you just want to ask about how Go works, please see https://golang.org/wiki/Questions.

@beoran thanks for your response.
Although there is more structure, but it can solve this problem.
@ianlancetaylor
i only want to solve this problem.
beoran's response helps me.