texhex / sqlsimpleps Goto Github PK

In case you try to use a SQL template where the last column ends with "D", e.g.:

DELETE FROM [schema].[TestTable] WHERE IssueID = @IssueID;

SQLSimplePS will generate incorrect SQL like this (the "D" got deleted):

DELETE FROM [schema].[TestTable] WHERE IssueID = @IssueI;

This seems to be related to the TrimEnd(" AND ") command used in SQLSimplePS.psm1

In some cases, an array list containing hash tables does not cut it, so it should be possible that SQLSimplePS returns a nested hash table.

We need to specify a parameter which field will be used as Key for the hash table.

$sqls = [SQLSimple]::CreateFromConnectionStringFile()
$sqls.AddCommand("select * from [my].[Table]")
$results = $sqls.Query()

#Create empty hash table
$eouDates = @{ }

foreach ($row in $results)
{
    #The key is the name to have easy access
    #The value is the hash table
    [void]$eouDates.Add($row.Name, $row)
}

This is not supported for .Data, but we should document it

Some system level commands can not be executed in a transaction, so SQLSimplePS should support running commands without transactions.

E..g. when $sqls.TransactionIsolationLevel = [System.Data.IsolationLevel]::Unspecified then do not use transactions at all.

This command would clear all commands attached to the current instance but keep the database connection. I believe there are many cases this would be useful as this would allow the reuse of an existing instance over and over again.

Since often the column name in a mapping and the SQL column name are the same, this would make usage in these cases easier.

If the source item is not found inside a mapping, we should also include some existing properties of that object so the operator knows where to look.