Content Changes

Author: sathishk

content/docs/guides/basics.md

@@ -6,6 +6,6 @@ draft: false
 
 **SQL Components** simplifies how your Java application interacts with relational databases by providing three core concepts:
 
-1. **Manager**: Handles database connections and manages access to various database objects.
+1. **DataManager**: Handles database connections and manages access to various database objects.
 2. **Model**: Represents the structure of database tables as simple Java objects (POJOs).
 3. **Store**: An interface that allows you to perform common database operations like **Select**, **Insert**, **Update**, and **Delete** on tables.

content/docs/guides/table.md

@@ -4,7 +4,13 @@ weight: 10
 draft: false
 ---
 
-Store will act as inteface for all the SQL operations againts tables.
+Store will act as inteface for all the SQL operations againts tables. For.eg For Movie table, you can get the Store from DataManages as given below
+
+```java
+MovieStore movieStore = DataManager.getManager().getMovieStore();
+```
+
+From here you can execute SQL Statements against the table as follows
 
 ## Insert
 

content/docs/why/_index.md

@@ -6,7 +6,9 @@ toc: true
 
 Before diving into the "why," let’s first understand the problem SQL Components aims to solve.
 
-Consider a simple Java application that connects to a relational database like PostgreSQL to create a movie store. The database schema looks like this:
+> Consider a simple Java application that connects to a relational database like PostgreSQL to create a movie store.
+
+The database schema looks like this:
 
 ```sql
 CREATE TABLE movie (
@@ -20,14 +22,14 @@ Now, let's add some movies:
 
 ```sql
 INSERT INTO movie (title, directed_by) VALUES
-('Inception', 'Christopher Nolan'),
-('The Dark Knight', 'Christopher Nolan'),
-('Interstellar', 'Christopher Nolan'),
-('Dunkirk', 'Christopher Nolan'),
-('Pulp Fiction', 'Quentin Tarantino'),
-('The Matrix', 'Lana Wachowski'),
-('Fight Club', 'David Fincher'),
-('The Social Network', 'David Fincher');
+        ('Inception', 'Christopher Nolan'),
+        ('Pulp Fiction', 'Quentin Tarantino'),
+        ('The Matrix', 'Lana Wachowski'),
+        ('Dunkirk', 'Christopher Nolan'),
+        ('Fight Club', 'David Fincher'),
+        ('Interstellar', 'Christopher Nolan'),
+        ('The Social Network', 'David Fincher'),
+        ('The Dark Knight', 'Christopher Nolan');
 ```
 
 Suppose you want to list the movies directed by `Christopher Nolan`. As a Java developer, your responsibilities include:

content/docs/why/jooq.md

@@ -33,7 +33,8 @@ Here’s how the same functionality looks with SQL Components:
 
 ```java
 List<Movie> movies = DataManager.getManager().getMovieStore()
-                        .select(directedBy().eq("Christopher Nolan"))
+                        .select()
+                            .where(directedBy().eq("Christopher Nolan"))
                         .returning();
 ```
 

content/docs/why/jpa.md

@@ -59,7 +59,8 @@ In SQL Components, the same query to list movies directed by a particular direct
 
 ```java
 List<Movie> movies = DataManager.getManager().getMovieStore()
-                        .select(directedBy().eq("Christopher Nolan"))
+                        .select()
+                            .where(directedBy().eq("Christopher Nolan"))
                         .returning();
 ```
 

content/docs/why/sql-builders.md

@@ -55,7 +55,8 @@ While SQL Builders abstract connection management, **SQL Components** offers add
 
 ```java
 List<Movie> movies = DataManager.getManager().getMovieStore()
-                        .select(directedBy().eq("Christopher Nolan"))
+                        .select()
+                            .where(directedBy().eq("Christopher Nolan"))
                         .returning();
 ```