Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Details page does not work with Npgsql 3.x (Postgre) #427

Closed
iboware opened this issue Dec 5, 2017 · 4 comments
Closed

Error Details page does not work with Npgsql 3.x (Postgre) #427

iboware opened this issue Dec 5, 2017 · 4 comments

Comments

@iboware
Copy link

iboware commented Dec 5, 2017

Postgre connection doesn't work with Npgsql 3.x. It connects and error list is visible, but the problem occurs only when you wanted to see the detail of an error.
Error: 42883: operator does not exist: character = uuid
Possible fix: npgsql/npgsql#1304

image

@atifaziz
Copy link
Member

atifaziz commented Dec 6, 2017

Paging @laimis who originally contributed the error log implementation for PostgreSQL.

@iboware
Copy link
Author

iboware commented Dec 6, 2017

Additional information about the bug, it seems that bug exists since 2015: npgsql/npgsql#753 (comment)

@iboware
Copy link
Author

iboware commented Dec 6, 2017

By changing the type of errorid column to uuid, I got it working with the existing code. Here is the DDL for elmah_error table:

CREATE TABLE public.elmah_error (
	errorid uuid NOT NULL,
	application varchar(60) NOT NULL,
	host varchar(50) NOT NULL,
	"type" varchar(100) NOT NULL,
	"source" varchar(60) NOT NULL,
	message varchar(500) NOT NULL,
	"User" varchar(50) NOT NULL,
	statuscode int4 NOT NULL,
	timeutc timestamp NOT NULL,
	"sequence" int4 NOT NULL DEFAULT nextval('elmah_error_sequence'::regclass),
	allxml text NOT NULL,
	PRIMARY KEY (errorid)
)
WITH (
	OIDS=FALSE
) ;
CREATE INDEX ix_elmah_error_app_time_seq ON elmah_error USING btree (application, timeutc DESC, sequence DESC) ;

@atifaziz
Copy link
Member

This issue has been migrated to elmah/PgsqlErrorLog#2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants