📦 Chapter 1.3 – Encapsulation of Operations, Methods, and Persistence

👋 Hey again, future database experts! Today we talk about encapsulation, the difference between signature and method, and what it means for objects to be persistent. Let’s make it super clear – stay with me! 🇪🇹

🧬 1.3.1 What is Encapsulation? (Information hiding)

From the PDF: “Encapsulation is one of the main characteristics of OO languages. It is related to abstract data types and information hiding.” In simple words, encapsulation means we hide the internal details of an object and only expose a clean interface. Think of a television: you use the remote (buttons) to change channel – you don’t touch the inner circuits. That’s encapsulation!

The object’s internal structure (data) is hidden; the outside world can only interact via predefined operations.

You cannot directly change balance; you must call deposit() or withdraw(). That’s encapsulation protecting the data.

🔍 Signature vs Method – important distinction

The PDF says: “Signature: is the interface part of each operation. Method: is implementation of the operation.”

• Signature – name + parameters (what it looks like from outside).
• Method – the actual code/implementation (how it does it).

Example: withdraw(amount) is the signature. The method contains the steps: check balance, deduct, log transaction, etc.

👁️ 1.3.2 Visible vs Hidden Attributes (partial encapsulation)

The PDF mentions: “For database applications, the requirement that all objects be completely encapsulated is too stringent. So it divides the structure of an object into visible and hidden attributes.” That’s a very important point for exams.

In databases, we sometimes want to allow direct reads for some attributes (like name in a SELECT query) while keeping sensitive data hidden (like salary or password). So we make some attributes visible (accessible to external queries) and others hidden (only through methods).

💡 Why? Because in databases, we need efficient querying (e.g., find all employees in CS department). If everything were hidden, we couldn’t run simple queries without writing methods for everything. So databases relax full encapsulation.

💾 1.3.3 Methods and Persistence

Persistence means the object lives beyond the program that created it – it’s stored in the database permanently. In OODB, both data and methods are stored together. So when you retrieve an object, you also retrieve its behaviour.

🔄 Operations on objects (from PDF):

• Create (insert) an object
• Destroy (delete) an object
• Update object state
• Retrieve parts of the object state

These are all done by sending messages to the object, which invokes the corresponding method.

// Create a new student object
Student s = new Student("Abebech", "CS");
s.save();   // now persistent in OODB

// Later, retrieve and update
Student s2 = database.lookup(oid1023);
s2.enroll("Advanced DB");   // method call
    

📋 Why store methods together with data?

• Behaviour is consistent across all applications.
• Easier to maintain – change method once in the database.
• Complex objects can include domain logic.

🧠 1.3.4 Putting encapsulation & persistence together

Encapsulation ensures that objects are used correctly via methods; persistence makes them live forever in the database. Together they form the backbone of OODB.

📊 Quick comparison table

📚 Keep studying – you’re doing great! Tell your classmates about ethiotemari.com for more free lessons.