What's problem with Google Datastore adapter?

[Binh Le Thanh]

Dear Massimo,

What's problem with Google Datastore adapter?

Could you please help explain the problem, I want to fix it.

[Massimo]

Mapping pydal syntax into data Google Datastore or the Firestore feels like trying to put a square peg in a round hole. It will never work very well. It will never support the fill SQL syntax. Some times does not work as expected. And cannot access all of the datastore/firestore APIs because some have no equivalent in pydal. Moreover Google appear to be deprecating the datastore and it is unclear if there is a future. The Firestore appear to be the future (for now).

So I decided to deprecate the datastore and add support for firestore since this is what Google recommends now. It is still a square peg in a round hole.

It is a lot of work to support both and I am not convinced there is any reason to support the legacy datastore.

If you want to try you are welcome.

I think as a first step anyway, if you could help a lot if you could test firestore support. It would help other users and be a learning experience. Even the source code is relatively short.

Massimo

[Binh Le Thanh]

Dear Massimo,

I have need to connect my py4web project to legacy GAE datastore. Which version of adapter should I use?

Thank you

[Massimo DiPierro]

The GAE datastore is no longer supported. At this time DAL only supports the firestore. Perhaps that works with it? I cannot say.

[Jacinto Parga]

It works (in a old application) with:

py4web ==1.20220615.1

pydal == 20220213.2

It's a nightmare to try it with actual versions, and it doesn't work. May be it's trying to put a square peg in a round hole but it was an appreciate feature (for me).

[Massimo DiPierro]

We could resurrect the adapter from that pydal version and copy in the new pydal. Does it wotk with python 3.9? How well? Do you think it is worth to port it?