Devart Forums

StanislavK

Could you please send us a small project with the problem?

As far as I could understand, you are using the only OracleConnection for multiple DataTables and this connection is somehow set at design-time. Since OracleConnection is a reference type, its properties can be changed once in any DataTable.Connection and this will affect all other DataTables. Please let me know if I've missed something.

StanislavK

Please try adding the following code to the System.Data node of your machine.config file:

Code: Select all

(replace 4.65.57.0 here with your actual version).

For more information, please see the Deployment section in our help:
http://www.devart.com/dotConnect/PostgreSQL/docs/ .

StanislavK

You can set a reference to the connection put on another form either at design-time or at run-time. At design-time you can refer to the connection by some other component (like OracleDataTable) and then edit OracleDataTable.Connection. At run-time you can get the connection directly like this:

Code: Select all

OracleConnection con = (OracleConnection)Devart.Common.GlobalComponentsCache.GetObjectByName ("YourDataForm.YourConnection");

Please let us know if this helped.

StanislavK

To resolve the problem with converting MySqlDecimal you can try creating your own conversion function, e.g.

Code: Select all

class MyConverter
{
    public static decimal ToDecimal(object value)
    {
        if (value is MySqlDecimal)
            return (decimal)((MySqlDecimal)value);
        else return System.Convert.ToDecimal(value);
    }
}

Though this solution is not completely one-point, at least you'll be able to auto-replace Convert.ToDecimal with MyConverter.ToDecimal.

As for DBNull issue, you can use the IsNull property casting objects like ds.Tables[0].Rows[0]["Percent_Owned"] to System.Data.SqlTypes.INullable interface.

StanislavK

The decimals stored in databases have trailing zeros as it is the way MySQL represents them. The decimals stored in DataTable are of the .NET type "decimal" which has no information about their precision. Thus, when the decimals from DataTable are displayed, e.g. in some Grid class, they are converted to strings by the standard ToString() method.

Probably, the provider you've previously used had specific ToString() conversion which added trailing zeros. dotConnect for MySQL doesn't have such functionality, hence we can only advice you to customize the controls in which you display data.

StanislavK

That's correct: just add to the licenses.licx file both lines

"Devart.Data.Oracle.OracleConnection, Devart.Data.Oracle"

and

"Devart.Data.PostgreSql.PgSqlConnection, Devart.Data.PostgreSql"

and then compile the licenses resourse as usual.

StanislavK

Unfortunately, the design-time support of multiple queries for TableAdapter is not available now. We will consider the possibility of adding such functionality in one of the future dotConnect for PostgreSQL versions.

At the moment you can add more queries e.g. to the custom DataTable class. Thus, if you've generated a custom DataSet class CustomDataSet and corresponding DataTable class CustomDataSet.CustomDataTable, it will be something like

Code: Select all

using Devart.Data.PostgreSql;

namespace YourApplicationNamespace
{
    public partial class CustomDataSet
    {
        public partial class CustomDataTable
        {
            public decimal getCount()
            {
                PgSqlCommand command = new PgSqlCommand(
                    "select count(*) from Your_Table", Connection);

                try
                {
                    if (Connection.State !=System.Data.ConnectionState.Open) 
                        Connection.Open();
                    object ret = command.ExecuteScalar();                    
                    return (decimal)ret;
                }
                catch
                {
                    return -1;
                }
                finally
                {
                    Connection.Close();                  
                }                
            }
        }
    }
}

StanislavK

1) I've tested the sample with Oracle client and DBMS version 11.

2) Please provide us your email address so that I'd be able to send you the exact project.

3) We recommend our customers to use the latest version of the Oracle client.

4) To check whether code in the sample works you should check if the message sent to the server returns to the subscribed event.

StanislavK

The error occurred while inserting multiple rows will cancel the whole operation because the OracleCommand.ExecuteArray function uses array DML operations.

StanislavK

Thank you for your report, we have reproduced the error. It will be fixed in the nearest build.

At the moment you can manually clean the \Program Files\Devart\dotConnect folder and remove all Devart.* and policy.*.Devart.* files from your GAC.

StanislavK

It seems that the problem really was connected with the different styles of line breaks. Please note that they are parsed on the database side and not inside the OracleCommand class.

StanislavK

Please specify versions of dotConnect for Oracle and Oracle DBMS you are using.

I've tested your code using Oracle database versions from 9 to 11 and the latest 5.35.57 build of dotConnect for Oracle. It created the table Devarttestparam, inserted a row into it, selected this row, showed it in a message box and then dropped the table.

I can send you a small project so that you'd be able to show the possible inexactitudes in reproducing the issue.

StanislavK

Please specify your connection string, Oracle client version and call stack for the error you receive.

Also, I can send you a small project. Please change it so that we'll be able to reproduce the error.

We couldn't reproduce the problem at the moment.

StanislavK

Unfortunately, we couldn't reproduce the error.

If you've made any changes in the sample, please send us a test project.

Otherwise, please note that the sample is a multi-threaded application and the error most likely occurs in threads invoking the getMessageData function.

Besides, please specify if 10.1.0.2 is the version of your Oracle client, Oracle DBMS or both.

StanislavK

We have investigated the problem. As ORA-28002 is an informational message and actually not an error, it throws no exception.

We have added the functionality to trace the message, it will be available in the next build. ORA-28002 will invoke the OracleConnection.InfoMessage event, and the Code property of the corresponding OracleInfoMessageEventArgs object will contain the message code (i.e. 28002).

Search found 1710 matches