CosminCioranu commented on issue #21038:
URL: https://github.com/apache/superset/issues/21038#issuecomment-2321061675
I can confirm it works.
The issues arises sometimes in 4.x at least on fresh install with
mariadb+galera.
Please find below a small script to adjust the values.
set @lastVar=(SELECT lastval(ab_permission_view_id_seq));
set @nextVar=(SELECT nextval(ab_permission_view_id_seq));
set @mm=(select max(id) m FROM ab_permission_view);
select @mm, @lastVar, @nextVar, if (@lastVar<@mm,@mm,@lastVar) setTo;
EXECUTE IMMEDIATE CONCAT('SELECT SETVAL(`ab_permission_view_id_seq`, ', @mm,
',true)');
> Hi all, It might be help you. I have resolved it by checking the max seq
id value of ab_permission_view_role table and update
nextval(ab_permission_view_role_id_seq) table by using below command.
>
> * SELECT nextval('ab_permission_view_role_id_seq')
> * SELECT currval('ab_permission_view_role_id_seq')
> * SELECT max(id) FROM ab_permission_view_role
>
> After update it, the superset init is back to normal.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org
