App Platform not automatically getting the database schema changes.

The issue is that whenever I make changes in the database, such as adding a new column in any table, or anyother change that result in schema change, these changes are not immediately picked by the APP platform. but if I query the database using PGAdmin or view the content of the database using prisma studio these new columns are there.

For example; I recently created assignees column in the task table and if I view the table from prisma studio I can see that there is a assignees column . but the error that I’m getting in the Runtime logs of the lobster-app platform stats that there is no assignees column.

This has happened before too and I haven’t still got satisfactory answer to why that is happening. Sometimes it got fixed when it detach and reattach the database BUT that’s not a solution to the problem and as I’m using a “Dev Database” in the lobster-app there is no option to detach and reattach the database.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev
Site Moderator
Site Moderator badge
April 1, 2023

Hi there,

That is very interesting, what is the exact framework that you are using? Usually I would recommend avoiding making schema changes to your database manually, but using database migrations within your app itself.

It sounds like that your database changes are either not being committed, or somehow your app is caching the results hence not picking up the new changes.

I could suggest two things:

  • Try using another tool like DBEver to make your database changes to verify that you can see those in both PGadmin and in DBever
  • If the above is not the problem, try clearing the cache of your application or trigger a redeployment to make sure that there is no cache on the local ephemeral storage left.

Feel free to share more details on the framework or the CMS that you are using so I could advise you furhter!



Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

card icon
Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Sign up
card icon
Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help.

Learn more
card icon
Become a contributor

You get paid; we donate to tech nonprofits.

Learn more
Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow – whether you’re running one virtual machine or ten thousand.

Learn more ->
DigitalOcean Cloud Control Panel