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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,467,920
Community Members
 
Community Events
177
Community Groups

Adding index and Not Null to existing table causing problems.

Edited

We are currently going through the Atlassian Data Center app readiness checklist and are a little confused by what is required for Questions 89, 90, and 91 - Database: Additional Tables

We found that we did require indexes on our additional tables, which works fine. However, when we add a NOT NULL constraint to the indexed fields, on updating the app in the host application the existing tables are dropped, recreated and all data is gone. Obviously, this is not suitable for our existing customers. 

This does not happen if we only add the Index and no further constraint. 

So this leads me to ask, is the NOT NULL constraint for an indexed column absolutely necessary?

Question 89 is:

Does your app have indexes defined on the fields that are used in frequent queries? *
I now can answer Yes to this. 

Now, reading question 90 of the checklist:

 Does your app have non­null constraints and unique constraints to guarantee? *

I read this to be asking, does your app have nonnull constraints and unique constraints to guarantee the index of the previous question. 

Is this how others are reading it? This is what led me to believe the NOT NULL constraint goes hand in hand with the index. 

Any advice or previous experience would be greatly appreciated. 

Marina
 

1 answer

0 votes

For a bit more context (I've got three ways I could be reading the question), could you tell us what "DC Checklist" you are using?  Typing some of the phrases you have used into google does not land me on any documentation, so I'm a bit lost on what you're reading.

Hi Nic

I'm referring to the Atlassian Data Center app readiness checklist.

It was originally a google form. 

 

Marina.

Like Nic Brough -Adaptavist- likes this

Thanks, that's cleared up what I suspected - it's not something I have run into myself (I've not written DC apps).  But it saves us suffering the other essay-like answers that don't apply!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events