Support multiple Actual server versions at once

[bvanelli]

Description

As described in #51 (comment), mhe main issue is that I intended to support multiple versions on Actual, but sqlalchemy emit statements for all columns when doing an insert. For example, when inserting a payee:

E       [SQL: INSERT INTO payees (id, name, category, transfer_acct, favorite) VALUES (?, ?, ?, ?, ?)]
E       [parameters: ('835983d9-1e5e-4c24-bca5-55acea558f2c', None, None, '99293e48-4f92-4d92-a1f1-cd4f4c126d22', None)]

This code works fine for actual 24.8.0, but not on 24.7.0, because there the column favorite does not exist. I tried using sqlalchemy deferred column but that is only effective on selects, not inserts.

This is extremely annoying because I then need either:

• Multiple models of the database, one per version, and deciding each one on the go when connecting to the server or
• Have "templated" models that would load the attributes lazily, but only when they are confirmed to exist on the database

I like the second idea more, but it's a bit difficult to implement.

[rodriguestiago0]

Why not just support the latest version?

If you want a older version you can just use an older version of actualpy

[bvanelli]

@rodriguestiago0 this is what I'm currently doing, the issue with just reverting to an older version is that I don't actually label them so, so it's hard to know to which version you should revert to.

But for sure I'm not considering implementing this in the near future, because the challenge is quite big, since i would have to modify how sqlalchemy emits queries.

[rodriguestiago0]

Can we release it with the api latest version?

[bvanelli]

Can we release it with the api latest version?

Maybe I did not understand what you meant, but you suggested releasing the supported Actual APIs versions on the releases page?

[rodriguestiago0]

Create a new release for the latest actual budget version.

[bvanelli]

I believe the current version already supports latest 24.11.0. The only change I did since then was the optimization when redownloading the files.

[rodriguestiago0]

I’m using the latest version and I’m getting an error.

[rodriguestiago0]

The latest version was released before the 24.11.0 was released.

[bvanelli]

Could you provide details in a new issue? Seems like a bug to me.

[rodriguestiago0]

""Actual found a column not supported by the library: column 'Name' at table 'payees' not found\n""

[bvanelli]

I assumed you typed this by hand since the upper case should not be there for 'Name'. Could you open an issue and place s reproducible script of what you are trying to do?

[rodriguestiago0]

No, I'm using https://github.com/bobokun/actualtap-py and I'm getting this error

[rodriguestiago0]

"Actual found a column not supported by the library: column 'Name' at table 'payees' not found\n"
Error occurred when
with Actual(settings.actual_url, password=settings.actual_password, file=settings.actual_budget) as actual:

[bvanelli]

@rodriguestiago0 are you able to check the version of the library by importing it in your script?

import actual

print(actual.__version__)

If that is the latest version I would need to know which row change is failing.

[rodriguestiago0]

Version: 0.7.0

How can I know the row?

[bvanelli]

Version: 0.7.0

How can I know the row?

You can update the print slighly on the part that is failing:

                if column is None:
                    raise ActualError(
                        f"Actual found a column not supported by the library: "
                        f"column '{message.column}' at table '{message.dataset}' not found, {message}\n"
                    )

But I believe that this will not be helpful, as it seems to me like the column somehow got corrupted due to some other issue with actual. Can you try resetting the budget sync like described in the docs https://actualbudget.org/docs/settings/#reset-sync and see if that helps?