Applies prefix twice on nested sublevel
See original GitHub issueBecause the prefix is applied on open:
So if you open, close and reopen, self.prefix = subdb.prefix + self.prefix happens twice.
There are more issues with the open logic (#60, #77), so let’s refactor it a bit.
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Wildcard SSL certificate for second-level subdomain
I'd like to know if any certificates support a double wildcard like *.*.example.com ? I've just been on the phone with my current...
Read more >Amazon Redshift Data Loading Behavior | Stitch Documentation
Nested data scenarios - These scenarios apply when Stitch loads nested data into Redshift. Direct data warehouse changes - These scenarios apply when...
Read more >classic-level - NPM Package Overview - Socket - Socket.dev
If name is empty, the effective prefix is two separators. Sublevels can be nested: if db is itself a sublevel then the effective...
Read more >Prefix for nested configuration properties in spring
I tried to add Qualifier or ConfigurationProperties with a prefix address but it is not working. Unfortunately, I cannot find useful information ...
Read more >Multilevel numbering in Word that works perfectly, first time
Each level of a multilevel numbering system can be linked to a style. This means that as you apply styles throughout the document,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

cheers: looks like its working well and I have about five sub-levels too. Thanks for the quick fix.
4.1.4