Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Facebook
Downloads
Home
>
mailing lists
PATCH: resolved an issue occured in cast creation - Mailing list pgadmin-hackers
From
Sanket Mehta
Subject
PATCH: resolved an issue occured in cast creation
Date
January 19, 2016
14:46:16
Msg-id
CA+yw=mOOgm4mAsj+rG2HmyeyVtBroArWN8FWkdrumEqYL9wBOg@mail.gmail.com
Whole thread
Raw
Responses
Re: PATCH: resolved an issue occured in cast creation
(Dave Page <dpage@pgadmin.org>)
List
pgadmin-hackers
Tree view
Hi,
I have resolved an issue, occurred while creating a new cast.
ISSUE:
While creating a new cast, when user select source type and target type, below query is used to fetch the function list related to that cast.
SELECT proname, nspname
FROM pg_proc p JOIN pg_namespace n ON n.oid=pronamespace
WHERE proargtypes[0] = <oid of source type>
AND proargtypes[1] = 0
AND prorettype = <oid of target type>
In this query "proargtypes" contains argument type list.
As you can see above proargtypes[1] (2nd argument to function ) is compared to 0 (in bold)
But according to postgresql standard, "proargtypes" field comparison should be like this :
proargtypes[1] (if present) should be compared to 23 (int4),
and proargtypes[2] (if present) should be compared to 16 (bool).
I have resolved the issue and patch is attached with this mail.
Please do review it and let me know in case of anything is missing.
Regards,
Sanket Mehta
Sr Software engineer
Enterprisedb
Attachment
pgadmin_cast_creation_issue.patch
pgadmin-hackers
by date:
Previous
From:
Surinder Kumar
Date:
19 January 2016, 14:28:49
Subject:
PATCH: NodeAjaxOptionsControl - Empty dropdown not working
Next
From:
Ashesh Vashi
Date:
19 January 2016, 15:25:45
Subject:
pgAdmin 4 commit: Initialize and parse the neseted schema too.
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
I confirm that I have read and accepted PostgresPro’s
Privacy Policy
.
I agree to get Postgres Pro discount offers and other marketing communications.
✖
×
×
Everywhere
Documentation
Mailing list
List:
all lists
pgsql-general
pgsql-hackers
buildfarm-members
pgadmin-hackers
pgadmin-support
pgsql-admin
pgsql-advocacy
pgsql-announce
pgsql-benchmarks
pgsql-bugs
pgsql-chat
pgsql-cluster-hackers
pgsql-committers
pgsql-cygwin
pgsql-docs
pgsql-hackers-pitr
pgsql-hackers-win32
pgsql-interfaces
pgsql-jdbc
pgsql-jobs
pgsql-novice
pgsql-odbc
pgsql-patches
pgsql-performance
pgsql-php
pgsql-pkg-debian
pgsql-pkg-yum
pgsql-ports
pgsql-rrreviewers
pgsql-ru-general
pgsql-sql
pgsql-students
pgsql-testers
pgsql-translators
pgsql-www
psycopg
Period
anytime
within last day
within last week
within last month
within last 6 months
within last year
Sort by
date
reverse date
rank
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
By continuing to browse this website, you agree to the use of cookies. Go to
Privacy Policy
.
I accept cookies