rhnChannelFamilyServerVirtual_synonyms.sql
rhnUserAvailableChannels_grants.sql
On Sun, Feb 22, 2009 at 10:08 AM, Gurjeet Singh
gurjeet.si...@enterprisedb.com wrote:
Done with almost all the views. Only three views are left for porting.
Apart from these three, 18 views that have been converted had
of files
ls postgresql/views/ | while read LINE; do echo
***$LINE**; diff rhnsat/views/$LINE postgresql/views/$LINE
1/dev/null; echo $? ; done
On Mon, Mar 2, 2009 at 1:46 PM, Gurjeet Singh
gurjeet.si...@enterprisedb.com wrote:
The three pending views have also been ported and pushed
Hi All,
The object EVR_T has been ported to Postgres, and resides in
schema/spacewalk/postgres/class/evr_t.sql
Porting the object involved
.) Creating a TYPE evr_t.
.) Creating overloaded operators to compare two evr_t objects; these will
enable the ORDER BY to work on these objects.
.)
Done with almost all the views. Only three views are left for porting. Apart
from these three, 18 views that have been converted had to be commented from
the main.sql since these views use either packages or the object EVR_T. So
started on package migration.
The changes have been pushed to pgsql
Hi All,
Am opting in for the Monday's optional holiday. Will be reachable on
cellphone, and will have intermittent access to mails.
Best regards,
--
gurjeet[.sin...@enterprisedb.com
EnterpriseDB http://www.enterprisedb.com
singh.gurj...@{ gmail | hotmail | indiatimes | yahoo }.com
Vikram, apparently, there are quite a few schema changes and additions in
this merge. Can you please look at the diff and make appropriate changes to
the postgresql/tables/ directory?
Some tables have been replaced by views, I'll take care of porting these
views.
Farrukh, we have some procedures
I am using upper case to highlight the usage of keywords. We otherwise
should not be using uppercase in this porting effort.
.) Datatypes:
We follow the same rules for converting datatypes that we followed in
porting tables.
number = numeric (for now, until we convert tables' number
with us the dependency list of
procedures as you did for tables.
Thanks and best regards,
On Thu, Feb 12, 2009 at 4:56 PM, Gurjeet Singh
gurjeet.si...@enterprisedb.com wrote:
I am using upper case to highlight the usage of keywords. We otherwise
should not be using uppercase in this porting
On Thu, Feb 12, 2009 at 5:47 PM, tushar tushar...@gmail.com wrote:
Gurjeet Singh wrote:
I am using upper case to highlight the usage of keywords. We otherwise
should not be using uppercase in this porting effort.
.) Datatypes:
We follow the same rules for converting datatypes that we
Hi Jeff,
This is the mail I was talking about in the last con-call. Please
provide your thoughts on these issues.
Best regards,
On Thu, Jan 22, 2009 at 5:59 PM, Gurjeet Singh
gurjeet.si...@enterprisedb.com wrote:
.) Orafce support for Postgres 8.1:
I am unable to find any concrete
Hi All,
As I mentioned in the last conference call, I could not implement a
workaround for CONNECT BY in plpgsql; that was because of a limitation in
the way plpgsql handles the pseudo datatype RECORD.
So, I turned to implementing it as an add-on in C. But I wanted to
actually see how
2009/2/6 Michael Mraka michael.mr...@redhat.com
CONNECT BY creates a tree select. Can the above select with
rhn_get_action_prerequisites() handle multi level dependencies as well?
I.e. for
id prerequisite
1 NULL
2 1
3 1
21
On Fri, Feb 6, 2009 at 7:50 PM, Devan Goodwin dgood...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 6 Feb 2009 19:37:28 +0530
Gurjeet Singh gurjeet.si...@enterprisedb.com wrote:
Hmm.. Although that is doable, I haven't thought about that. The way
I saw
On Fri, Feb 6, 2009 at 7:30 PM, Devan Goodwin dgood...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 6 Feb 2009 18:22:49 +0530
Gurjeet Singh gurjeet.si...@enterprisedb.com wrote:
Hi All,
As I mentioned in the last conference call, I could not implement
On Thu, Feb 5, 2009 at 11:42 PM, Jesus M. Rodriguez jes...@redhat.comwrote:
+ spacewalk/vikram
This should be removed too. It was pushed accidentally by Vikram yesterday.
Vikram, please make a local copy and confirm the removal.
Best regards,
--
gurjeet[.sin...@enterprisedb.com
EnterpriseDB
On Tue, Feb 3, 2009 at 5:40 PM, Jan Pazdziora jpazdzi...@redhat.com wrote:
On Tue, Feb 03, 2009 at 04:21:29PM +0530, Gurjeet Singh wrote:
_query_latest_version = rhnSQL.Statement(
SELECT nvl(version, 0) version, version orig_version, cert,
TO_CHAR(issued, '-MM-DD
On Tue, Feb 3, 2009 at 7:00 AM, Devan Goodwin dgood...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey guys, blocked on another spot in the installer and wanted to queue
these items up for porting:
Out of backend/satellite_tools/satCerts.py:
_query_latest_version =
On Tue, Feb 3, 2009 at 6:34 PM, Jan Pazdziora jpazdzi...@redhat.com wrote:
On Tue, Feb 03, 2009 at 06:26:19PM +0530, Gurjeet Singh wrote:
How about
order by decode(version, null, 1, 0), version
Yup... that'll work, but will mess up the ordering if more than one
I am starting to work on the following set of tables:
schema/spacewalk/rhnsat/tables/rhnAction*.sql
Best regards,
On Tue, Feb 3, 2009 at 12:47 PM, Gurjeet Singh
gurjeet.si...@enterprisedb.com wrote:
Hi All,
I have migrated the following DB objects to work okay with Postgres:
./procs
Hi All,
I have migrated the following DB objects to work okay with Postgres:
./procs/create_first_org.sql
./tables/web_customer.sql
./tables/rhnUserGroupType.sql
./tables/rhnUserGroup.sql
./tables/rhnOrgQuota.sql
./tables/rhnUserGroup_sequences.sql
./tables/rhnServerGroupType.sql
Can you post the exact error message you got?
From the looks of it, I think following are the issues with it:
1) In Postgres we have to CREATE FUNCTION RETURNS VOID.
2) rhn_user_group_id_seq.nextval is being used, so we need to port that
Sequence too.
Will be doing this in about an hour from
Reading up on 'Exit Status' section in
http://www.postgresql.org/docs/8.3/static/app-psql.html shows that it will
return 3 if ON_ERROR_STOP was set, and it was run using a script.
So I guess you need to do it as:
my $psql_cmd = PGPASSWORD= . $password . psql -U .
$user . -h . $host . .
Thats good news. We will need more QA for the features provided by orafce.
Can we have an optional pseudo package (something like spacewalk_postgres )
that spacewalk package would depend on, so that we make postgres and orafce
part of those and 'yum install spacewalk_postgres' will automatically
Hi All,
I followed the guide at
https://fedorahosted.org/spacewalk/wiki/DevelopmentWorkstationSetup and
tried to setup a dev env on CentOS 5.2.
Here's what I started with:
Clean install of CentOS, with a few packeges that make sense for
Spacewalk like webserver, etc.
Disable
.) Orafce support for Postgres 8.1:
I am unable to find any concrete documentation on Orafce, apart from the
README in the sources. So can't comment on the deficiencies it'd have if
ported to PG 8.1.
.) Empty string in queries. ('')
The proposed solution of putting a CHECK constraint
Hi All,
Just finished Wikifying the initial guidelines on how to go about
porting to Postgres. You can find it here:
https://fedorahosted.org/spacewalk/wiki/PostgresPortingGuidelines
These are my opinions on the issues I could see directly (in schema/ or
through grepping). There are
26 matches
Mail list logo
