Date problem w/ Mono running on a Mac

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for PostgreSQL
Post Reply
Guest

Date problem w/ Mono running on a Mac

Post by Guest » Tue 15 Nov 2005 01:54

I have a .NET application that runs on the Mac using the Mono Project. All the data looks good except for dates. They are coming back as an empty string or 01/01/01.

using 2.20.12
DB engine 8.01

Any thoughts?


(also, works fine as .NET app and using Mono on WinXP)

SecureGen
Devart Team
Posts: 133
Joined: Thu 08 Sep 2005 06:27

Post by SecureGen » Tue 15 Nov 2005 09:47

It is a new issue. I need more information about your environment in order to analyze the problem.
Please answer following questions:
- Do you connect to the same PostgreSQL server in both cases?
- Do you have PostrgeSQL server installed on Windows or Mac platform?
- Which protocol do you use for connection?
- Did you try to access this data using strandard tools like pgAdmin? Did you see your datetime fields?

ComputerAidedTech
Posts: 4
Joined: Tue 15 Nov 2005 01:48

Post by ComputerAidedTech » Tue 15 Nov 2005 17:50

- Do you connect to the same PostgreSQL server in both cases?
Yes

- Do you have PostrgeSQL server installed on Windows or Mac platform?
Mac

- Which protocol do you use for connection?
TCP/IP (not sure if this is what you are looking for)

- Did you try to access this data using strandard tools like pgAdmin?
Yes, from both the Mac and XP

Did you see your datetime fields?
Yes - the data looks ok. I did notice that the field I am looking at is a TimeStamp, so I added Date field with the same results.

SecureGen
Devart Team
Posts: 133
Joined: Thu 08 Sep 2005 06:27

Post by SecureGen » Mon 21 Nov 2005 10:23

We have investigated this situation. In the last version we have problem converting date datatypes using binary ptotocol on Linux and MAC OS. We are going to fix it in the next build.
Now you can try to use the text protocol in you PostgreSQL connection. You should set ";Protocol=2" option in your connection string;

ComputerAidedTech
Posts: 4
Joined: Tue 15 Nov 2005 01:48

Still does not work - Protocol=2

Post by ComputerAidedTech » Tue 22 Nov 2005 15:59

Still does not work - Protocol=2.

I added a IsDBNull check and it is always returning false.

Is this related to the issue?

Did someone verify that setting the Protocol=2 would work?

What is the ETA of this fix? I now have a "hot" client that keeps calling.

ComputerAidedTech
Posts: 4
Joined: Tue 15 Nov 2005 01:48

Any word on a fix for this?

Post by ComputerAidedTech » Sat 10 Dec 2005 19:05

For kicks I tried to use 2.4, but the MonoProject does not have all the .NET 2.0 implmented, so I got an error when loading System.Data.Common.DbConnection.

I also tried your protocol=2 suggestion and that did not work. What am I missing?

I just got another email from my client.

I have to find a soltuon ASAP.

Any thoughts?

SecureGen
Devart Team
Posts: 133
Joined: Thu 08 Sep 2005 06:27

Post by SecureGen » Mon 12 Dec 2005 10:51

Using the text protocol (protocol=2) is the most compatible way of working with Postgre SQL server on different platforms. Our tests of text protocol with mono do not produce any errors. Please try to use this protocol in your application. If you will have any problem please send me error message and simple example that reproduces your problem. (DDL that creates table with necessary datatypes, and code piece that shows what you are trying to do).

ComputerAidedTech
Posts: 4
Joined: Tue 15 Nov 2005 01:48

Post by ComputerAidedTech » Tue 13 Dec 2005 18:44

There is no error. The date field is always returning IsNULL.

I'll see what I can put together for you.

SecureGen
Devart Team
Posts: 133
Joined: Thu 08 Sep 2005 06:27

Post by SecureGen » Fri 16 Dec 2005 09:53

We are looking forward for your example (small DDL and code).

Post Reply