From 88ab371fe6cb662bc691f800943dd057bde10e14 Mon Sep 17 00:00:00 2001 From: Kishalay Pandey Date: Sun, 21 Jan 2024 23:12:15 +0530 Subject: [PATCH] #1596:Updated README.md --- slob/README.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/slob/README.md b/slob/README.md index 33251499335e..a2c23449fb70 100644 --- a/slob/README.md +++ b/slob/README.md @@ -33,15 +33,17 @@ tag: ## Applicability +* This pattern works best when you can chop out a piece of the object model and use it to represent + the LOB. +* Think of a LOB as a way to take a bunch of objects that aren’t likely to be queried from any SQL + route outside the application. +* This graph can then be hooked into the SQL schema. Serialized LOB works poorly when you have + objects outside the LOB reference objects buried in it. * Serialized LOB isn’t considered as often as it might be. XML makes it much more attractive since - it yields a easy-to-implement textual approach. + it yields an easy-to-implement textual approach. * Its main disadvantage is that you can’t query the structure using SQL. * SQL extensions appear to get at XML data within a field, but that’s still not the same (or portable). -* This pattern works best when you can chop out a piece of the object model and use it to represent - the LOB. Think of a LOB as a way to take a bunch of objects that aren’t likely to be queried from - any SQL route outside the application. -* This graph can then be hooked into the SQL schema. ## Credits