Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

ActiveObjects problem with multiple schemas.

It is well known that ActiveObjects technology does not play well with multiple schemas in database.

Atlassian advice is to have separate database for each JIRA instance:


There are also similar problem with Bitbucket:


Recently we have started to use ActiveObjects technology for database model migrations on cloud environments where the library deals with thousands of schemas of PostgreSQL >9.6 database.


We were faced with improving the library to handle multiple schemas. It turned out to be pretty simple for PostgreSQL. In class getFields method jdbc driver DatabaseMetadata.getColumns method had passed null as schema name. Funny, because several lines further DatabaseMetadata.getPrimaryKeys method passed schema name as result of databaseProvider.getSchema(). 


Improving getting columns data by passing databaseProvider.getSchema() as schema name resolved the problem.


Why this improvement was not implemented by Atlassian? Does it conflict some database type/version?



Log in or Sign up to comment