DatabaseObjects | .NET Object Relational Mapping Tool

ConnectionStringExcel is initialized using filename but it won't track future changes.

You can convert ConnectionStringExcel into a readonly property with this getter

I am still unclear what you want. I will assume from the picture that you want the column “SrNo” to have the numbers 1, 2, 3… etc.… instead of the “pre-sorted” index order. This is doable; however, it appears there may be some confusion as to setting a cell value in the “grid” as opposed to setting a cell value in the data source.

Example, looking at the first code snippet the code gets a DataTable dTable from a data base. Then the code adds a column to the GRID. Then the data source is set to the grid. Then the GRID is sorted. Finally, a loop through all the rows in the GRID to set the SrNo values. This is straight forward and from my tests… this SHOULD WORK. You state that the column is empty however in my tests this code worked as expected with 1, 2, 3 … in the “SrNo" column. It is unclear where this code is called so I would conclude something else is going on after this code is called.

As other have commented, it may be better to put the column into the DataSource DataTable itself. This is doable, however, there is one problem from the approach you are using… you need to SORT the data table FIRST before you add the “SrNo” Numbers AND the table that we add the ”SrNo” column to CAN NOT be sorted. Therefore, you need to get a “new” table from the “sorted” table.

It is unclear why you do not do all this when you initially query the data base, however, below is an example of what I described above.

To start let us see “why” we can NOT use a “pre” sorted DataTable to add the numbers to. First, we get a data table. Then sort the data table, then use it as a data source to the grid. If we add the new column to the GRID, then… this works just fine. However, if we add the column to the DataTable and loop through all the rows in the data table like…

you are inversing the steps :

• open the connection;
• check is there is comming data;
• check if the value is not null;
• read the data;

try this :

"Section" is a reserved word in MS Access, so its use here is confusing the query parser.

You can explicitly tell the query what identifiers are referring to database objects (columns, tables, etc.) by wrapping them in square brackets:

I've come up with a way to deal with this problem. Thanks to mongoose https://mongoosejs.com/ I was able to communicate with mongoDB via it's functions. Thus I was able to create a standalone .ts file, create classes to access Controller's and Service's methods.

Next I used Nodejs's Child_Process fork(), and this way I had a working async functionality.

I think the main issue with this solve is repetitive code, this way we will need to update schemas each time they are updated in the rest code.

I would override equals and hashCode in both of my Enties which hold the three attributes groupId, artifactId, version then sort the two List based on the three arrtibutes, and just use .equals to determine if the two Lists are equivalent or no :

It's necessary to study all of the related/linked pages of the Db2 Knowledge Center for your Db2-version that describe C# .net common language runtime procedures.

Start here and study every linked page, make the examples work on your environment.

If your Db2-server runs on Microsoft-Windows, or if you installed the Windows-specific Db2-samples with your full data-server-client (default location is:

\program files\ibm\sqllib\samples\dotnet\cs

) then you can see the DataTable examples for C# there, and also online in the Knowledge-Center - "DbDatMap.cs" and related files and "SpClient.cs" and its dependencies

Please check why you populate DataTable DT but return DTT.

If you debug your code you should be able to iterate over rows in DT after the da.Fill(DT); completes successfully.

A consoleApp using most of your syntax works fine for me, the only variations being that I used a pre-existing connection, and supply a varchar parameter to my stored procedure instead of integer (but that cannot make a difference).

Extending PDO is never the "best practice". Actually it's the exact opposite. And traits are just a code-smell, since they are interpreter-driven copy-paste.

IMHO, the best approach is to separate the business logic and the persistence logic. For example: you have a class that does the user-logic and a separate class that saves or populates the instance of this user class. This pattern is called data mapper.

Basically the setup goes like this:

PHP is a quite forgiving language, in that certain language constructs and practices are not as strictly applied as in other programming languages.

PHP does not complain if you provide more parameters than a class method expects, whether that method is a costructor or regular method. See below, which outputs "Hello World!" just fine: