You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When installing Parse Server with PostgreSQL 10, adding Config entries to ParseDashboard will result in deletion of the old Config entries, i.e. Config can only put one entry. After checking the database, it is found that each new Config entry objectId is 1.
Steps to reproduce
Before adding new entries:
then add new one:
add success and refresh page:
the db record:
Expected Results
There was originally a configuration item,after adding an entry, there should be two configuration items.
Actual Outcome
In fact, only new configuration items are added after the old ones are replaced.
Environment Setup
Server
parse-server version (Be specific! Don't say 'latest'.) : 3.0.0
Operating System: unknown , like heroku PaaS platform,sina cloud SAE service
Hardware: unknown
Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): remote, sina SAE
Database
PostgreSQL version: 10.0
Storage engine: S3
Hardware: unknown
Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc):remote ,Aliyun RDS
Logs/Trace
The text was updated successfully, but these errors were encountered:
Issue Description
When installing Parse Server with PostgreSQL 10, adding Config entries to ParseDashboard will result in deletion of the old Config entries, i.e. Config can only put one entry. After checking the database, it is found that each new Config entry objectId is 1.
Steps to reproduce
Before adding new entries:
then add new one:
add success and refresh page:
the db record:
Expected Results
There was originally a configuration item,after adding an entry, there should be two configuration items.
Actual Outcome
In fact, only new configuration items are added after the old ones are replaced.
Environment Setup
Server
Database
Logs/Trace
The text was updated successfully, but these errors were encountered: