Search found 4 matches

by calfonso
Mon 05 Mar 2012 12:35
Forum: dotConnect for MySQL
Topic: DataContext & Memory Leaks
Replies: 17
Views: 7554

DataContext & Memory Leaks

Hi StanislavK,

We are with a lot of problems in a production environment, related with this problem. We are stuck waiting for a solution.

You discovered something about. Could you put a high priority in this task and publish the modifications in the next release?
Could you provide me, in private, some phone number to contact the suport team? (This is not published in your web site).
If you don't have a solution in a short time we'll be forced to change our provider (i think it's not a good solution).

thanks in advance
by calfonso
Wed 15 Feb 2012 16:19
Forum: dotConnect for MySQL
Topic: DataContext & Memory Leaks
Replies: 17
Views: 7554

Hi StanislavK,

I'm with the same problems described by luigisaggese but using SQLServer or Oracle DB with LinqConnect version 3.1.25.

The latest release (LinqConnect 3.1.34) solved this?

ps.: let me know when the corresponding build is released. ok

Thanks in advance.
by calfonso
Fri 15 Oct 2010 20:31
Forum: LinqConnect (LINQ to SQL support)
Topic: Argument types do not match when map char(1) to System.Char
Replies: 2
Views: 2066

Argument types do not match when map char(1) to System.Char

Hello,
I'm testing a trial version of LinqConnect and I get a System.ArgumentException when I have a nullable char(1) column in any table.

To reproduce this you need:
1- create a table in a sqlSever
CREATE TABLE [dbo].[TestTable](
[Id] [int] IDENTITY(1,1) NOT NULL,
[Status] [char](1) NULL)

2- generate a new DataContext with this table;
3- Run any query like this one:
{
DataContextSql dataContext = new DataContextSql();
var entity = dataContext.TestTables.First();
}

Could you help me?
Thank you.
by calfonso
Mon 30 Aug 2010 17:41
Forum: dotConnect for Oracle
Topic: dotConnect for Oracle v5.70 implementation suggestion
Replies: 4
Views: 1475

What do you think of using the same interfaces created by microsoft like ITable, IQueryable, etc instead of creating their own interfaces?
With this we could