Skip to main content

Multimedia data support in commercial DBMS

There are three kinds of DBMS that is available Commercially:
1.      Relational DMBS (RDBMS)
Oracle support three large object types that are used to store multimedia data types with Oracle InterMedia:
a.       BLOB (Binary Large Objects):
                                                              i.      Stores unstructured binary data in database
                                                            ii.      Can store up to 4 GB
b.      CLOB (Character Large Objects)
                                                              i.      Single-byte character set data
                                                            ii.      Sores up to 4GB
c.       NCLOB (National character set Character Large Objects)
                                                              i.      Fixed-width and varying width multi-byte national character set data
                                                            ii.      Stores up to 4 GB
Relational databases are efficient for numeric and textual data store, but do not conventionally support content based searches for multimedia content.

Example:
CREATE TABLE image_blob_table (
id NUMBER  PRIMARY KEY,
image_blob BLOB
);

INSERT INTO image_blob_table (id, image_blob)
VALUES (1, “<path_of_image>”);

2.      Object-Oriented DBMS (OODBMS)
Jasmine is an Object-Oriented database that stores the data in form of built in classes and objects. It comes with built in classes to include four multimedia classes:
a.       Picture
b.      Image
c.       Video
d.      Audio
These comes with manipulation and compression facilities. They also have been made to fit will with Java Media Framework
3.      Object-Relational DBMS (ORDMBS)

The BFILE data type in Oracle provides access to BLOB files up to 4 GB that are stored in file systems outside an Oracle database. The BFILE datatype allows read-only support of large binary files, you cannot modify a file through Oracle. Oracle provides APIs to access file data.

Comments

Popular posts from this blog

SAP-1(Simple as Possible-1) Computer Architecture Introduction

The Simple-As-Possible (SAP)-1 computer is a very basic model of a microprocessor explained by Albert Paul Malvino. The SAP-1 design contains the basic necessities for a functional Microprocessor. Its primary purpose is to develop a basic understanding of how a microprocessor works, interacts with memory and other parts of the system like input and output. The instruction set is very limited and is simple. The features in SAP-1 computer are: W bus – A single 8 bit bus for address and data transfer.  16 Bytes memory (RAM)  Registers are accumulator and B-register each of 8 bits.  Program counter – initializes from 0000 to 1111 during program execution.  Memory Address Register (MAR) to store memory addresses.  Adder/ Subtracter for addition and subtraction instructions.  A Control Unit  A Simple Output.  6 machine state reserved for each instruction  The instruction format of SAP-1 Computer is (XXXX) (XXXX) A Simple animation ...

[FIX]Illuminate\Database\QueryException SQLSTATE[HY000] [2054] The server requested authentication method unknown to the client (SQL: select * from information_schema.tables where table_schema = enrolmentsystem and table_name = migrations and table_type = 'BASE TABLE')

Illuminate\Database\QueryException    SQLSTATE[HY000] [2054] The server requested authentication method unknown to the client (SQL: select * from information_schema.tables where table_schema = enrolmentsystem and table_name = migrations and table_type = 'BASE TABLE')   at vendor/laravel/framework/src/Illuminate/Database/Connection.php:678     674▕         // If an exception occurs when attempting to run a query, we'll format the error     675▕         // message to include the bindings with SQL, which will make this exception a     676▕         // lot more helpful to the developer instead of just the database's errors.     677▕         catch (Exception $e) {   ➜ 678▕             throw new QueryException(     679▕                 $query, $this->prepareBindings($binding...