Page 1 of 1

LinqConnect Professional Version 4.4.453 (06-Mar-2014) - Problems with CreatDatabase (PostgreSQL)

Posted: Wed 12 Mar 2014 12:00
by AKRRKA
Hello,

Already have a problem with create database from code and from Entity Developer, but now with PostgreSQL.

System info:
PostgreSQL 9.3.3 (2014-02-20) x64
Windows 7 x64 Pro Ru
When create database from Entity Developer:

Code: Select all

-- Table: "SysInfos"

-- DROP TABLE "SysInfos";

CREATE TABLE "SysInfos"
(
  "SysInfoId" serial NOT NULL,
  "DBVersion" integer NOT NULL,
  "DTChange" timestamp without time zone NOT NULL,
  "MetrologyIdentification" character varying NOT NULL,
  "RefVersion" integer NOT NULL,
  "SoftVersion" integer NOT NULL,
  "TimeOfUse" character varying NOT NULL,
  CONSTRAINT "PK_SysInfos" PRIMARY KEY ("SysInfoId")
)
WITH (
  OIDS=FALSE
);
ALTER TABLE "SysInfos"
  OWNER TO postgres;
When create database from code CreateDatabase():

Code: Select all

-- Table: "SysInfos"

-- DROP TABLE "SysInfos";

CREATE TABLE "SysInfos"
(
  sysinfoid serial NOT NULL,
  dbversion integer NOT NULL,
  dtchange timestamp without time zone NOT NULL,
  metrologyidentification character varying NOT NULL,
  refversion integer NOT NULL,
  softversion integer NOT NULL,
  timeofuse character varying NOT NULL,
  CONSTRAINT "PK_SysInfos" PRIMARY KEY (sysinfoid)
)
WITH (
  OIDS=FALSE
);
ALTER TABLE "SysInfos"
  OWNER TO postgres;
"SysInfoId" vs sysinfoid
PostgreSQL is case-insensitive!

For code:

Code: Select all

var sysInfos = _dataContext.SysInfos.FirstOrDefault();
generated SQL code:

Code: Select all

SELECT t1."SysInfoId", t1."DBVersion", t1."DTChange", t1."MetrologyIdentification", t1."RefVersion", t1."SoftVersion", t1."TimeOfUse"
FROM "SysInfos" t1 LIMIT 1
1) And get error wen send to database created from code with CreateDatabase().
2) Moreover it would be good specify a schema before names of tables and fields.

Code: Select all

SELECT
"public"."SysInfos".sysinfoid,
"public"."SysInfos".dbversion,
"public"."SysInfos".dtchange,
"public"."SysInfos".metrologyidentification,
"public"."SysInfos".refversion,
"public"."SysInfos".softversion,
"public"."SysInfos".timeofuse
FROM
"public"."SysInfos"
Schema name is set in the connection string.

In addition put my screenshot:
Link to full image
Image

This for me is a very important issue please fix as soon as possible.
Thanks.

Re: LinqConnect Professional Version 4.4.453 (06-Mar-2014) - Problems with CreatDatabase (PostgreSQL)

Posted: Wed 12 Mar 2014 12:04
by AKRRKA
3) And do not add comments to tables and fields as when creating a database from Entity Developer same from code with CreateDatabase().

Re: LinqConnect Professional Version 4.4.453 (06-Mar-2014) - Problems with CreatDatabase (PostgreSQL)

Posted: Fri 14 Mar 2014 12:14
by MariiaI
"SysInfoId" vs sysinfoid
We have reproduced this issue. We will inform you when it is fixed.
As for your other comments, we will consider them and contact you as soon as any results are available.

Re: LinqConnect Professional Version 4.4.453 (06-Mar-2014) - Problems with CreatDatabase (PostgreSQL)

Posted: Fri 25 Apr 2014 05:26
by MariiaI
The bug related to the incorrect script generation for column names (lower case) when working with the CreateDatabase()/DeleteDatabase() methods is fixed.
New build of LinqConnect 4.4.484 is available!
It can be downloaded from http://www.devart.com/linqconnect/download.html (trial version) or from Registered Users' Area (for users with active subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?f=31&t=29439.

Re: LinqConnect Professional Version 4.4.453 (06-Mar-2014) - Problems with CreatDatabase (PostgreSQL)

Posted: Wed 07 May 2014 13:55
by AKRRKA
1) Issue with lower case resolved, I confirm.
Thank you.

2) If possible ask to consider the schema name in queries.
3) And comments.

Re: LinqConnect Professional Version 4.4.453 (06-Mar-2014) - Problems with CreatDatabase (PostgreSQL)

Posted: Thu 08 May 2014 08:51
by MariiaI
AKRRKA wrote: 2) If possible ask to consider the schema name in queries.
3) And comments.
We will definitely post here when these features are implemented.