$Conflict$ $equivalent$ $Schedules$ should be $Serial$ $Schedule$, &
$View$ $equivalent$ $Schedules$ should be $Serial$ $Schedule$
then we can conclude that
$All$ $Conflict$ $serializable$ $schedules$ $are$ $also$ $view$ $serializable$
We cannot directly determine
$View$ $equivalent$ schedule from $Conflict$ $equivalent$ Schedules, It MUST be $Serial$ $Schedule$,
Two schedules are said to be conflict equivalent if all the conflicting operations in both the schedule get executed in the same order
If a schedule is a conflict equivalent to its serial schedule then it is called Conflict Serializable Schedule
Conflict schedule should be serial schedule then we can conclude that is it View serializable equivalent or not.
A schedule is said to be View-Serializable if it is view equivalent to a Serial Schedule (where no interleaving of transactions is possible)