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

When running restore from bee, the sessions table is wiped out #148

Open
argiepiano opened this issue Dec 22, 2023 · 2 comments
Open

When running restore from bee, the sessions table is wiped out #148

argiepiano opened this issue Dec 22, 2023 · 2 comments

Comments

@argiepiano
Copy link
Collaborator

This is a follow up to #115

BAM (by default) doesn't include the sessions table in backed up database. When you restore from the UI, the old session table is somehow preserved intact, but restoring from bee wipes out its content. I'm not sure how and why this is happening. It may very well be that sessions building is being prevented when running bee.

@yorkshire-pudding
Copy link

When bee runs it tells Backdrop that is a CLI operation through the backdrop_is_cli() function. That may then tell Backdrop to do something different.

@izmeez
Copy link

izmeez commented Jan 23, 2024

Isn't this simply because by default BAM does not drop all tables before doing a restore. So while BAM backup did not preserve a sessions table, the site continued using the existing session table. Since restore also does not drop all tables before a restore (unless configured to do so) the session table remains as do any others through out the site, such as caches etc. So, I'd say this is normal behaviour. Maybe bee is doing override with drop tables before bam restore?

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