Tag Info

New answers tagged

1

MS Access Vs MySQL MS Access works only on Windows whereas MySQL works on almost all platforms. MS Access does not support Partitioning feature whereas MySQL has composite, Range partitioning support. MySQL is opensource so no cost involved. Performance in MySQL is way better than MS Access MS Access database is more suitable for desktop use with a small ...


1

As well as PostgreSQL (which I recommend), you could also look at Firebird (another excellent choice). What is your development environment? If you're replacing spreadsheets, another good option might be Oracle's APEX with Oracle XE. If you do decide to go down the MySQL route, try to avoid non-standard data types like SET and ENUM (porting becomes ...


0

Take a look at http://www.mysql.com/why-mysql/windows/excel/ MS Access has limitations, data types, storage size, users access control (since you're going to have it accessed by more than a user). i think using MySQL will be more useful as your database grows up. it is a powerful dbms and will open doors for future enhancements and migrations.


3

Redundancy does not mean: Columns that have the same data type Columns (or rows) that have the same data value (if this is coincidental) Columns that are foreign keys that link a child table to its parent (including the same data value as FK and PK in the respective tables) Redundancy is not about columns or rows for that matter. Redundancy is about ...


0

You should consider using a real indexed search engine such as elasticsearch with runs on Java, uses a REST interface with json and so is exceedingly easy to program to, is free and open source, with a good community behind it. www.elasticsearch.org You could have it running on the same server as your application as long as you have a decent enough machine ...


0

Yes. ALTIBASE HDB - HybridDB DRAM DB and Disk DM SQL standards compliant, supports all common interfaces, HA, ACID in 1 single unified engine = 1 DB for both. For Caching difference please see: http://altibase.com/solutions/ For HybridDB product overview see: http://altibase.com/products/


0

Yes, you could use one table to track both sold and unsold items. It would be like a transaction table in an OLTP, with the distinction that the transaction remains open until the sale is closed. In theory that's a good idea, as that would be 3NF (assuming listings and sales are 1-1), but it practice it's more common to denormalize the for sale listings ...


0

You don't sell to users, you sell to parties (companies or individuals). Some might play the role of users. There are many parties involved in a sales/purchase order: the vendor (you if you sell) the buyer (you if you buy) a party selling something on consignment sales staff taking commission the party that placed the order the party that took the order ...



Top 50 recent answers are included