# How to override Django's internal use of "public" schema

**URL:** <https://forum.djangoproject.com/t/how-to-override-djangos-internal-use-of-public-schema/42117>\
**Category:** Using the ORM\
**Created:** [July 29, 2025, 5:57pm UTC](https://forum.djangoproject.com/t/how-to-override-djangos-internal-use-of-public-schema/42117 "2025-07-29T17:57:15Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![KenWhitesell](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/kenwhitesell/32/280_2.png) [@KenWhitesell](https://forum.djangoproject.com/u/KenWhitesell)\
**Post date:** [July 30, 2025, 3:10am UTC](https://forum.djangoproject.com/t/how-to-override-djangos-internal-use-of-public-schema/42117/2 "2025-07-30T03:10:16Z")

</div>

Welcome @rythazhur !

I suggest you see the thread at [Why won't Django look for my Postgres schema?!](https://forum.djangoproject.com/t/why-wont-django-look-for-my-postgres-schema/27852) .

In a standard / local PostgreSQL environment, it does work. However, the person asking the question in that topic identified that it was something in their hosting provider causing it to fail.

---

_[View the full topic](https://forum.djangoproject.com/t/how-to-override-djangos-internal-use-of-public-schema/42117)._
