It is a known good practice to keep only necessary indexes to reduce the write performance and disk space overhead. This simple rule is mentioned briefly in the official MySQL Documentation:https://dev.mysql.com/doc/refman/8.0/en/optimization-indexes.htmlHowever, in some cases, the overhead from adding a new index can be way above the expectations! Recently, I’ve been analyzing a customer case like […]
31
2024
MySQL Table Size Is Way Bigger After Adding a Simple Index; Why?
30
2024
PG_TDE Update: Percona’s Project to Add Transparent Data Encryption to PostgreSQL
PG_TDE is an experimental transparent data encryption access method for PostgreSQL 16 and beyond that I reviewed last October. There have been a lot of changes that covered in this post. This software is under active development. In the spirit of open and transparent communication, we would appreciate your feedback and invite PostgreSQL users to […]
30
2024
Master PostgreSQL Upgrades: The Ultimate Checklist
Are you planning to upgrade your PostgreSQL database but feeling overwhelmed by the complexity of the task? We have something that will make your life much easier. Introducing The Ultimate PostgreSQL Upgrade Checklist – designed to guide both seasoned and new DBAs and developers through the intricate process of a PostgreSQL upgrade.Why you need this […]
29
2024
Talking Drupal #435 – UI Suite initiative
Today we are talking about web design and development, from a group of people with one thing in common… We love Drupal. This is episode #435 UI Suite initiative.
For show notes visit: www.talkingDrupal.com/435
Topics
- Elevator Pitch
- What do you mean by implementing design systems
- Is this to thel themers or site builders
- What is the expected outcome
- The project page says initiative, but this is not on the community initiatives page, is this an intitiative
- How does this implement public design systems
- Does this work with Single Directory Components
- Youtube Channel
- Getting involved
- Roadmap
- Use cases
- Do you see this going into core
Resources
Guests
Pierre Dureau – LinkedIn pdureau
Hosts
Nic Laflin – nLighteneddevelopment.com nicxvan John Picozzi – epam.com johnpicozzi
MOTW Correspondent
Chris Wells – chrisfromredfin
- Brief description:
- Have you ever wanted simple but accessible dropdown navigation on your Drupal website? There’s a module for that.
- Module name/project name:
- Brief history
- How old: created in Nov 2022 by Jay Huskins of Redfin Solutions
- Versions available: 2.1.5 which works with Drupal 9 and 10
- Maintainership
- Actively maintained, most recent commit is less than a month ago
- No Test coverage at this point
- Documentation – via README.md
- Number of open issues: 2, neither of which are bugs
- Usage stats:
- 29 sites
- Maintainer(s):
- Jay Huskins, with support from Redfin
- Module features and usage
- Provides a new menu block that includes markup for disclosure buttons, that make it easier for users on assistive devices to navigate drop-down menus
- Activating the button will toggle the visibility of nested menu items
- Also includes ARIA labels to provide clarity around what the buttons do
- Worth mentioning that Drupal’s Olivero theme also includes disclosure buttons in its mWe’ll also cover Disclosure Menu as our module of the week.
- Guest Introenus, but there isn’t a straightforward way to pull the menus implemented there into your custom theme
- Also had a write-up in the Drupal advent calendar we talked about last month, so listeners can also check that out if they want more information
29
2024
Percona PG_TDE and Ubuntu: Please Test Transparent Data Encryption for PostgreSQL
PostgreSQL differs from certain other databases as it lacks a native solution to encrypt data on disk transparently. At Percona, we are in the process of developing PG_TDE, a tool designed to encrypt data using the AES-CTR encryption algorithm. This code is currently under development, and we are seeking your assistance in testing it.This blog […]
26
2024
Percona PG_TDE and Docker: Please Test Transparent Data Encryption for PostgreSQL
Securing your data can be a tough task. Unlike some other databases, PostgreSQL does not have a native solution to encrypt data on disk transparently. Percona is developing PG_TDE to encrypt that data using the AES-CTR encryption algorithm. This code is in development, and we need your help testing it.This blog will cover what you […]
25
2024
Decoding Sequential Scans in PostgreSQL
In every database product, sequential scans or full table scans are often resource consuming, so almost all the developers and DBAs see such scans as a performance killer. In my opinion, this is a false perception or biased view. In many cases, sequential scans are proven to be a performance booster. However, due to a […]
24
2024
An Introduction to Vector Databases
Imagine that winter is coming to the south of the planet, that you are going on a vacation trip to Patagonia, and you want to buy some cozy clothes. You go to that nice searcher page that says “do no evil” and write in the search field “Jackets for Patagonia weather,” not thinking of a […]
23
2024
Common PostgreSQL Upgrade Errors and How to Avoid Them
Everyone usually welcomes an upgrade, whether it’s a new operating system on your phone, a first-class seat on a flight, or a revamped kitchen in your home. Upgrades typically mean improvement, which is true for PostgreSQL, as each new version of PostgreSQL brings updates and enhancements essential for your application’s optimal performance, stability, and security. […]
22
2024
Talking Drupal #434 – Talking Drupal
Today we are talking about te show itself. We’ll also cover Autosave Form as our module of the week.
For show notes visit: www.talkingDrupal.com/434
Topics
- Update on the show
- Guest hosts
- MOTW Correspondent
- Newsletter
- Sponsorship
- Open Collective
- Content
- New content in 2024
- Expanding team
Resources
Hosts
Nic Laflin – nLighteneddevelopment.com nicxvan John Picozzi – epam.com johnpicozzi Stephen Cross – stephencross.com stephencross
MOTW Correspondent
Martin Anderson-Clutz – mandclu
- Brief description:
- Have you ever wanted an autosave feature on your Drupal site’s forms, so content creators won’t lose their work if they accidentally close the window or lose power? There’s a module for that.
- Module name/project name:
- Brief history
- How old: created in Nov 2016 by Hristo Chonov of 1x Internet, who is also one of the organizers of Drupal Dev Days 2024 in Burgas
- Versions available: 8.x-1.4 which works with Drupal 9 and 10
- Maintainership
- Actively maintained, most recent comment less than 3 months ago
- Test coverage
- 38 open issues, 20 of which are bugs
- Usage stats:
- 6,414 sites
- Module features and usage
- Works by automatically saving the content of the current form every 60 seconds, though the time period is configurable
- When a user opens a form, if an autosaved state exists for that form a dialog will be shown asking if they want to resume editing or discard any autosaved states
- Once a form is submitted, any saved states will be automatically deleted
- Notionally it should work with both content entity forms and config forms, but the majority of development and testing has been with entity forms in mind
- The project page also mentions an issue with nested entity reference inline forms, and has links to relevant Drupal core issues
- Worth noting that this module uses AJAX to save the states to the Drupal database, separate from entity revisions
- If you want a solution that save form states into the browser’s localStorage instead, you can check out the Save Form State module, using the jQuery Sisyphus plugin