Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maximum Number of Instance bug #37

Open
andreadetti opened this issue Apr 18, 2020 · 3 comments
Open

Maximum Number of Instance bug #37

andreadetti opened this issue Apr 18, 2020 · 3 comments

Comments

@andreadetti
Copy link

mni property of containers is not properly handled. When the number of content instances in a container becomes greater than mni then any other content instance can not be added (or better it is immediately cleaned). In my opinion, the issue seems related to the fact that in the sql database, cnt table, the cni value is not updated after delete_oldest in sql_actions.js

@dima91
Copy link

dima91 commented Dec 10, 2020

Hi guys, do you have any update about this issues? I encountered the same problem.

@woorinet
Copy link

woorinet commented May 28, 2021

이거 버그로 보이네요 수정이 필요합니다
mni 설정을 하면 cni가 mni보다 커지는 순간부터 데이터가 막 사라니다.
cnt 테이블의 cni값은 계속해서 증가하고 정작 조회해보면 데이터는 다 삭제되거나 한두개 남아있거나 합니다.
코드를 보면 mbs설정을 해도 동일한 문제가 발생할 것 같습니다.

@woorinet
Copy link

woorinet commented Jun 8, 2021

sql_action.zip
source file that fixed this bug. try this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants