In addition, support for JDBC and ODBC standard drivers allows you to connect to virtually any database.īase integrates seamlessly into the rest of the Apache OpenOffice suite applications, for example: When a personal use database is all you need, Base offers the full HSQL relational database engine, configured for single user, with the data stored right in the Base file, as well as native support for dBase flat files.įor power users in the enterprise, Base delivers native support drivers for a variety of multi-user database engines: MySQL, Adabas D, MS Access and PostgreSQL. This can make sure that all new entries, regardless of who did it, must follow the rules of your database.Base is a fully featured desktop database management system, designed to meet the needs of a broad array of users, from tracking a personal CD collections, to producing a corporate monthly departmental sales reports.īase offers wizards to help users new to database design (or Base) to create Tables, Queries, Forms and Reports, along with a set of predefined table definitions for tracking Assets, Customers, Sales Orders, Invoices and much more. If it’s essential that a record contain a certain field (in our example, and employee MUST have an ID number) make sure to set Entry Required to True for that field, as in the screenshot above. If you chose the fields from the dropdown menus in the wizard, these types should be automatically applied to the right fields. A number like EmployeeID makes sense as an integer, and text fields like first and last name should be text (CHAR or VARCHAR).
On the second page of the Table Design wizard, you specify what type of data will go into that field. There’s (probably) no chance of two employees having the same ID number, so it makes a perfect primary key. That may sound confusing, but it typically just means that you need a column like EmployeeID, and each entry has a different, unique number.
In short, this means that tables should generally have a column where each row in that column is unique on that table. Secondly, it’s important for tables to have a primary key. If you find yourself putting anything into a table that does not match with the title of that table (like Employee or Billing), it probably belongs in a different table. For starters, each table should represent only one idea – ie the Employee table should not contain shipping information. Database design is far too large a subject to cover here in detail, so we’ll just mention a few basics and leave some links at the bottom of this page for more detail.
0 kommentar(er)
