Pros of sql-server-samples

• More comprehensive coverage of SQL Server features and scenarios
• Better organization with clear categorization of samples
• Includes samples for various SQL Server versions and tools

Cons of sql-server-samples

• Less focus on performance optimization techniques
• Fewer examples of advanced database administration tasks
• Limited coverage of cloud-specific features compared to Oracle's examples

Code Comparison

sql-server-samples:

CREATE PROCEDURE dbo.usp_GetEmployeeManagers
    @EmployeeID INT
AS
BEGIN
    WITH EmpCTE AS (
        SELECT EmployeeID, ManagerID, FirstName, LastName
        FROM HumanResources.Employee
        WHERE EmployeeID = @EmployeeID
        UNION ALL
        SELECT e.EmployeeID, e.ManagerID, e.FirstName, e.LastName
        FROM HumanResources.Employee e
        INNER JOIN EmpCTE ecte ON ecte.ManagerID = e.EmployeeID
    )
    SELECT EmployeeID, FirstName, LastName
    FROM EmpCTE
END

oracle-db-examples:

CREATE OR REPLACE PROCEDURE get_employee_managers(
    p_employee_id IN NUMBER
) AS
BEGIN
    FOR rec IN (
        SELECT employee_id, first_name, last_name
        FROM employees
        START WITH employee_id = p_employee_id
        CONNECT BY PRIOR manager_id = employee_id
    ) LOOP
        DBMS_OUTPUT.PUT_LINE(rec.employee_id || ' ' || rec.first_name || ' ' || rec.last_name);
    END LOOP;
END;
/

Pros of postgres

• Open-source and community-driven development
• More extensive codebase with full database engine implementation
• Active and frequent contributions from a diverse developer base

Cons of postgres

• Steeper learning curve for contributors due to larger codebase
• Less focused on providing specific examples for users
• May require more setup and configuration for testing and development

Code Comparison

postgres:

/* in src/backend/access/heap/heapam.c */
HeapTuple
heap_fetch(Relation relation, Buffer buffer, ItemPointer tid,
           SnapshotData *snapshot, bool *all_dead)
{
    Page		page;
    ItemId		lp;
    HeapTupleData	tuple;

oracle-db-examples:

-- in sql/analytical-sql-examples/row_pattern_matching/01_basic.sql
SELECT *
FROM Ticker MATCH_RECOGNIZE (
  PARTITION BY symbol
  ORDER BY tstamp
  MEASURES STRT.tstamp AS start_tstamp,
           LAST(DOWN.tstamp) AS bottom_tstamp,
           LAST(UP.tstamp) AS end_tstamp

The postgres repository contains the full database engine implementation in C, while oracle-db-examples focuses on SQL examples and use cases. postgres offers a comprehensive look into database internals, whereas oracle-db-examples provides practical SQL patterns for Oracle Database users.

Pros of mongo

• Open-source project with a large community of contributors
• Flexible document-based data model for easier schema evolution
• Native support for horizontal scaling and sharding

Cons of mongo

• Less mature and feature-rich compared to Oracle's enterprise-grade offerings
• Limited support for complex transactions and joins
• Potential performance issues with large datasets and complex queries

Code Comparison

mongo:

db.users.insertOne({
  name: "John Doe",
  age: 30,
  email: "john@example.com"
})

oracle-db-examples:

INSERT INTO users (name, age, email)
VALUES ('John Doe', 30, 'john@example.com');

The mongo example demonstrates its flexible document structure, allowing for easy insertion of nested data without predefined schemas. The oracle-db-examples snippet showcases the traditional SQL syntax for inserting data into a relational database.

While mongo offers simplicity and flexibility, oracle-db-examples provides a more structured approach with stronger data consistency guarantees. The choice between the two depends on specific project requirements, scalability needs, and the development team's expertise.