Page 1 of 1

Database Limitation when exporting

Posted: Wed Oct 14, 2015 8:48 pm
by Sami

Hello,

I'have to create some reports with my database.

I saw that is not possible to retrieve the fields "createdAt" and "updateATt" when exporting database in CSV or JSON.

First Question : Is there a way to retrieve these fields in a databse export ?

Cause I can't have these "date" fields (it's necessary for my reporting), i decided to make a "side" app to export my Appery.io Database to a mysql Database (with appery express) but i found a limitation and i can only retrieve 1500 rows when i call a database_service

Second Question : Is there a way to get all my object without limitation when i call a service (it's not to use in a mobile app but to export my Apperyio Database to a mysql databse cause i can't have the field "createdAt" and "updateAt" when i export my databse to Json or CSV)

Thanks you


Database Limitation when exporting

Posted: Thu Oct 15, 2015 9:29 am
by Illya Stepanov

Hi Sami -

[quote:]
Is there a way to retrieve these fields in a databse export ?
[/quote]

No.

[quote:]
but i found a limitation and i can only retrieve 1500 rows when i call a database_service
[/quote]

That's correct, you can find this details here: https://devcenter.appery.io/documenta...

:: https://devcenter.appery.io/documenta...


Database Limitation when exporting

Posted: Wed Sep 28, 2016 3:42 pm
by Rich Slaby

These links are pretty generic. I'm not clear about whether the timestamp fields can be retrieved by some custom method if not as part of an export. If so, why doesn't Appery provide this functionality?


Database Limitation when exporting

Posted: Thu Oct 26, 2017 11:24 pm
by ssquire

Has this issue ever been addressed?


Database Limitation when exporting

Posted: Fri Oct 27, 2017 8:03 am
by Serhii Kulibaba

Appery.io exports only custom fields, IDs and ACL fields, but _createdAt and _updatedAt - not. They show the date of creation that field, so there is no way to reuse it.