Why borsh schema for Movie has different order of fields in serialize/deserialize

[SergeyDevyatkov]

Trying to understand, not explained anywhere, why the fields order is different in serialize and deserialize methods in movie model?

...
static borshSchema: borsh.Layout<Movie> = borsh.struct([
    borsh.u8("variant"),
    borsh.str("title"),
    borsh.u8("rating"),
    borsh.str("description"),
  ]);

  static borshAccountSchema: borsh.Layout<Movie> = borsh.struct([
    borsh.u8("initialized"),
    borsh.u8("rating"),
    borsh.str("title"),
    borsh.str("description"),
  ]);
...

[zarex5]

not only the order is different but variant/initialized are two very different properties (albeit of the same type)

• the 1st schema is an instruction schema, that you send to your program to execute an action
  • with 'variant' being used to choose witch action if you program handles multiple
• the 2nd is an account schema, that matches the storage account created by your program
  • with 'initialized' being used by your program to check if the account already exists

[SergeyDevyatkov]

@zarex5
so it means that when a new portion of data was committed to Solana backend, the Rust-written program itself was responsible for deserializing that data and storing it in this specific order (namely rating, title and description)?

[lalalazero1]

thanks for this issue.

I was having problems sorting the movies data. but I didn't notice the borsh schema was different.

now I understand more clearly for this process.