Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Architecture of Btrieve
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Micro-Kernel Database Engine==<!-- This section is linked from [[Database engine]] --> [[Image:MKDE model.svg|right|241px|thumb|The MKDE model allows for different database backends to be plugged into Pervasive's software product.]] Starting with version 6.15, Pervasive started using a new modular method of separating the database [[Back-end database|backend]] from the interface that developers used. They separated the core database operations (like update, write and delete records) from the Btrieve and [[Scalable SQL]] modules. By separating the Micro-Kernel Database Engine (MKDE) from the other functions it allowed [[programmer]]s to use several methods of accessing the database simultaneously. For instance, an application may be created using the Btrieve [[API]] and another [[Application software|application]] that needs to access the same data may use a totally different method, like using Scalable SQL. Because the [[Record (computer science)|record]] primitives have been separated from these methods, both applications can use the MKDE to access the same data [[Computer file|file]]. The Micro-Kernel Database Engine is unrelated to [[microkernel]] operating system kernels.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)