Discussion Overview
The discussion revolves around the need for a .NET library capable of reading and writing arrays of data tables from and to relational databases. Participants explore potential solutions and clarify the specific requirements for handling in-memory tables.
Discussion Character
- Exploratory
- Technical explanation
- Debate/contested
Main Points Raised
- One participant inquires about the existence of a .NET library for managing arrays of data tables in relational databases.
- Another participant suggests using Microsoft's Entity Framework (EF) as a general-purpose Object-Relational Mapping (ORM) library, though they express uncertainty about the specific requirements.
- A further response clarifies that the need is for persistence at the table level rather than field level, emphasizing the requirement for commands to read and write complete in-memory tables.
- The participant outlines a specific use case involving cost and margin tables for yearly calculations, illustrating the desired functionality with example commands.
- One participant mentions that they have not encountered such a library but believes it would be feasible to create one in .NET.
- The original poster later states that they have extended their existing non-commercial library to include a class named Persistent Table Array to handle the required database operations.
Areas of Agreement / Disagreement
Participants do not reach a consensus on the existence of a suitable library, with some suggesting alternatives and others proposing the development of a custom solution. The discussion remains unresolved regarding the availability of a pre-existing library.
Contextual Notes
The discussion highlights specific requirements for database operations involving in-memory tables, which may not align with typical ORM functionalities. There is also a mention of a custom solution being developed, indicating a gap in available resources.
Who May Find This Useful
Developers working with .NET who need to manage arrays of data tables in relational databases, particularly those focused on analytical operations and custom library development.