Feature/issue 16 add oracle suppport

[peter7775]

Description

Brief description of what this PR does and why it's needed.

Fixes # (issue number)

Type of Change

Please delete options that are not relevant and check the box that applies:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (changes to documentation only)
• Configuration change (changes to config files, docker setup, etc.)
• Code refactoring (no functional changes, just code improvements)
• Performance improvement
• Test updates (adding or modifying tests)

️ Changes Made

Core Changes

• Domain layer modifications (entities, aggregates, models)
• Application layer changes (services, ports)
• Infrastructure layer updates (repositories, database connections)
• API changes (REST endpoints, GraphQL schema)
• Configuration updates

Database Changes

• MySQL connection/query modifications
• Neo4j schema or query changes
• Data transformation logic updates
• Migration scripts added/modified

Visualization Changes

• Graph visualization improvements
• Frontend/UI modifications
• API response format changes

Testing

Test Coverage

• Unit tests added/updated
• Integration tests added/updated
• Manual testing completed
• Performance testing (if applicable)

Testing Checklist

• All existing tests pass (go test ./...)
• New functionality is covered by tests
• Manual testing with sample MySQL database
• Neo4j graph visualization works correctly
• API endpoints return expected responses
• Configuration changes tested

Test Environment

• MySQL Version:
• Neo4j Version:
• Go Version:
• Test Database Size:

Configuration

Configuration Changes

• New configuration options added
• Existing configuration modified
• Environment variables added/changed
• Docker configuration updated

Configuration Updates Required

# Example of new/modified configuration
# Remove this section if no config changes
mysql:
  # new settings...

neo4j:
  # new settings...

Deployment Notes

Breaking Changes

• Database schema changes required
• Configuration migration needed
• API contract changes
• Backward compatibility considerations

Deployment Steps

Performance Impact

• No performance impact expected
• Performance improvement expected
• Potential performance regression (explain below)
• Performance testing completed

Performance Details

• Memory usage:
• Query performance:
• API response times:
• Graph rendering performance:

Code Review Checklist

Code Quality

• Code follows project conventions and DDD architecture
• Functions and variables have meaningful names
• Complex logic is well-commented
• No hardcoded values (use configuration)
• Error handling is appropriate
• Logging is adequate

Security

• No secrets or credentials exposed
• Input validation implemented
• SQL injection prevention (prepared statements)
• Authentication/authorization considered

Architecture Compliance

• Changes follow Domain Driven Design principles
• Proper separation between layers (domain, application, infrastructure)
• Interfaces (ports) used appropriately
• Dependencies point inward (dependency inversion)

Screenshots/Examples

Before

After

Sample Output

// Example API response or configuration

Additional Notes

Related Issues

• Closes #
• Related to #
• Depends on #

Dependencies

• Requires new Go dependencies
• Requires infrastructure changes
• Requires configuration updates
• Requires documentation updates

Future Considerations

Pre-merge Checklist

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have verified the application starts and connects to databases successfully
• I have tested the graph visualization functionality
• Any dependent changes have been merged and published

️ Labels

Please add appropriate labels:

• bug, enhancement, documentation
• database, visualization, api, config
• performance, security, architecture
• needs-review, ready-to-merge

---

Reviewer Notes:

• Priority: High / Medium / Low
• Complexity: High / Medium / Low