___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
Gurjeet Singh wrote:
Hi All,
I am a bit late in doing this, but I think it is necessary, so here
it goes.
The migration of the Spacewalk project to support Postgres has
started, and EnterpriseDB is collaborating with Redhat and Spacewalk
developers on this. For now, the people
Jan Pazdziora wrote:
On Thu, Jan 15, 2009 at 03:36:55PM +0530, Gurjeet Singh wrote:
I am attaching the text file here. Lets discuss the issues here, and
finalize them, before going ahead with the actual modifications.
Thank you for the writeup. Here are my observations.
== Open
tushar ahuja wrote:
Hi,
I installed Spacewalk server(0.4) Successfully on RHEL-5 and Created the
Dev Environment too but at the time of deploying development Schema
Why are your running the make? The spacewalk install has already
created the schema.
Great!
Bruce Momjian wrote:
I tested Orafce 2.1.4 on Postgres 8.1 and found, aside from a few
regression test alignment differences, it works fine, so I think we can
move forward and use it. I am sure it will work fine on PG = 8.2 as
well.
___
Bruce Momjian wrote:
Jan Pazdziora wrote:
On Thu, Jan 29, 2009 at 11:45:42PM -0500, Bruce Momjian wrote:
Sorry, maybe I wasn't clear. On this page:
https://fedorahosted.org/spacewalk/wiki/PostgresTechnicalApproach
we list the four query types:
1. work unchanged in both Oracle
All,
We're in the process of formalizing the analysis/planning for the
postgres porting project. The project plan specifies this work to be
done in several iterations.
The 1st iteration generally consists of creating the postges schema and
porting those stored procedures not associated
Great Bruce! Thanks.
Bruce Momjian wrote:
The Orafce community has fixed their code so it runs fine on Postgres
8.1. Right now there is no orafce official release with these fixes so
we should use their CVS HEAD for our development. Once we near
completion we can request an official release
Very nice. Thanks for pointing it out - I need all the (git) help I can get :)
Devan Goodwin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Noticed in Fedora Weekly News there's some talk of replacing gitweb
with cgit for the Fedora infrastructure git web interface. They've got
it up
All,
I've added the view migration tracking table (
https://fedorahosted.org/spacewalk/wiki/PgportViews ) and linked to the tasks (
https://fedorahosted.org/spacewalk/wiki/PostgresTasks ) page. This table __is__ ordered
according to dependency.
-jeff
Thanks Devan!
Devan Goodwin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Made some updates this morning to the Git Guide in a number of areas,
most importantly I've changed the example workflow to (a) avoid the
goto master, pull, goto branch, rebase, goto master, merge, push dance
and
.
The changes have been pushed to pgsql branch and wiki page has been
updated. Will be adding a similar page for Package porting.
Best regards,
On Wed, Feb 18, 2009 at 9:24 PM, Jeff Ortel jor...@redhat.com
mailto:jor...@redhat.com wrote:
All,
I've added the view migration tracking table
Thanks for sending this out.
A couple of questions:
* Why did we abandon the tagging using number (1-5) and decide to go with
letters/words.
This seems more prone to error.
* Is the line # relative to the query? Like PGPORT_xx:3 for line #3 in the
query?
or is it the absolute line # in
been
updated. Will be adding a similar page for Package porting.
Best regards,
On Wed, Feb 18, 2009 at 9:24 PM, Jeff Ortel jor...@redhat.com
mailto:jor...@redhat.com wrote:
All,
I've added the view migration tracking table (
https://fedorahosted.org
Very nice! Thanks Muhammad.
Muhammad Farrukh wrote:
Hi All,
All the triggers have been migrated over to postgresql and main.sql has
also been changed to accommodate the trigger files.
The wiki has also been updated.
Regards,
Farrukh
, Feb 18, 2009 at 9:24 PM, Jeff Ortel jor...@redhat.com
mailto:jor...@redhat.com wrote:
All,
I've added the view migration tracking table (
https://fedorahosted.org/spacewalk/wiki/PgportViews ) and
linked to the tasks (
https
The following schema files are flagged to be EXCLUDED from the installed schema.
snip
31 # check if we need to include a SQL file
32 check-sql-file = $(shell egrep -i \
33 '^--[[:space:]]*EXCLUDE:[[:space:]]*(all|$(SCHEMA))' \
34 $(file) /dev/null 21 || echo $(file))
/snip
The
Yes, Mike is exactly right here.
The only reason to wrap a log.debug() in log4j is when passing the argument(s) is very
expensive and a simple (2) string concatenation doesn't qualify. Even passing an object
with an expensive toString() argument isn't a problem because the log4j lib is
Thanks for you comments!
Jan Pazdziora wrote:
On Tue, May 12, 2009 at 12:42:32PM -0400, Jeff Ortel wrote:
All,
I'd like to start getting some eyes on the pgsql branch in preparation of a
merge to
master. So far, the changes on this branch have been focused on porting the
schema
Jan Pazdziora wrote:
On Tue, May 12, 2009 at 12:42:32PM -0400, Jeff Ortel wrote:
The goal here was to push as much of the schema into common as practical and
make
the schema code tree as developer friendly as possible.
- The schema directory has been refactored replacing
rhnsat
Jan Pazdziora wrote:
Another email, focusing on the tables/ directory.
On Tue, May 12, 2009 at 12:42:32PM -0400, Jeff Ortel wrote:
- Table files (rhnsat/tables/*)
- table.sql files:
- Most moved to common/tables/
- Trigger DDL split out and moved into existing or new
oracle
Jan Pazdziora wrote:
On Tue, May 12, 2009 at 12:42:32PM -0400, Jeff Ortel wrote:
- Upgrades (upgrade/* directories files):
- Most files (git) moved to common/upgrade/upgrade
- Few files forked: (git) moved to oracle/upgrade/upgrade.
- Few files forked: copied to postgres/upgrade
Jan Pazdziora wrote:
On Tue, May 12, 2009 at 12:42:32PM -0400, Jeff Ortel wrote:
At build, common (common/) files are transformed by a build tool named
chameleon into DB
specific files. For example:
#
# cd oracle
# chameleon -s oracle -o tables/common/x.sql ../common/tables/x.sql
#
Long
Jan Pazdziora wrote:
On Tue, May 12, 2009 at 12:42:32PM -0400, Jeff Ortel wrote:
MAKEFILES
The Makefile.schema refactored into a /regular/ makefile. Dependency sorting
and .sql
file aggregation split out into a build tool named blend. Although, make
does do
dependency sorting
Jan Pazdziora wrote:
On Tue, May 12, 2009 at 12:42:32PM -0400, Jeff Ortel wrote:
PACKAGING
The spacewalk-schema.spec was updated to package and install install / upgrade
scripts for
both oracle and postgres. The files are installed in:
/etc/sysconif/rhn/oracle/
main.sql
spacewalk_0.4
Jan Pazdziora wrote:
On Thu, May 14, 2009 at 03:18:25PM -0400, Jeff Ortel wrote:
You cannot aggregate upgrade scripts because other products (like
Satellite) might want to address individual upgrade scripts (via
symlinks, or, work-in-progress, via references). There is a reason we
kept
Jan Pazdziora wrote:
On Thu, May 14, 2009 at 02:33:47PM -0400, Jeff Ortel wrote:
Note: I don't really care about the actual format, so I'm not voting
against the format per se (apart from the trailing spaces it seems to
introduce). We can put together some coding guidelines and use them
Michael Mraka wrote:
Jeff Ortel wrote:
% Jan, I appreciate you comments :)
%
% Jan Pazdziora wrote:
% On Thu, May 14, 2009 at 11:24:33AM -0400, Jeff Ortel wrote:
% The views/rhnHistoryView.sql file seems to still contain definition of
% rhnHistoryView_pkglist function. Is that correct
Milan Zazrivec wrote:
On Thursday 21 May 2009 22:23:17 Jeff Ortel wrote:
All,
The outcome of the meeting yesterday regarding the pgsql branch review is
as follows:
After lengthy discussion it was decided (almost unanimously by attendance)
that the work on the pgsql branch would be merged
Devan Goodwin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 21 May 2009 16:23:17 -0400
Jeff Ortel jor...@redhat.com wrote:
All,
The outcome of the meeting yesterday regarding the pgsql branch
review is as follows:
After lengthy discussion it was decided (almost unanimously
Jan Pazdziora wrote:
On Thu, May 21, 2009 at 04:23:17PM -0400, Jeff Ortel wrote:
After lengthy discussion it was decided (almost unanimously by attendance) that
the work
on the pgsql branch would be merged to master without refactoring the commits.
There
I would appreciate anything you
Milan Zazrivec wrote:
On Tuesday 21 July 2009 17:48:35 Jeff Ortel wrote:
All,
Yesterday I merged master-pgsql and today I'm planning on doing some
schema verification. Assuming that I can verify the schema (for oracle) is
equivalent, I will merge the pgsql branch TO master tomorrow 7/22
All,
I spend most of the day doing side-by-side verification of oracle schema installed from
master and pgsql. I've resolve most of the discrepancies and pushed them. I still have a
few to deal with, most of them straight forward. I also fixed a bug in chameleon and it
will have to be
Tom Lane wrote:
Jeff Ortel jor...@redhat.com writes:
One of the items that resurfaced is synonyms. The original plan was
to do away with the synonyms because postgres does not support them.
I've removed references to the synonyms in the schema (insert files)
but the monitoring code seems
In master, the 'web_user_pi_timestamp' trigger on 'web_user_personal_info' is
being defined in:
'rhnsat/tables/web_user_personal_info.sql' (SNIP#1)
Then redefined in (and the filename is all wrong):
'rhnsat/tables/web_user_contact_permission.sql' (SNIP#2)
The net effect is that the
Thanks for your participation :)
Milan Zazrivec wrote:
On Wednesday 22 July 2009 01:11:17 Jeff Ortel wrote:
[..]
|2 schema/spacewalk/common/tables/rhnSet.sql
|2 schema/spacewalk/common/tables/rhnSystemMigrations.sql
[...]
commit
Issues resolved and committed/pushed.
schema diff showing no discrepancies now.
Milan Zazrivec wrote:
On Wednesday 22 July 2009 01:32:51 Jeff Ortel wrote:
All,
I spend most of the day doing side-by-side verification of oracle schema
installed from master and pgsql. I've resolve most
All,
The pgsql branch has been merged to master. As most of you know, this involves some
changes in schema (source) directory structure, conventions and development procedures.
I'm working on a wiki page that defines these changes and procedures. Note: It is still a
work in progress.
Devan Goodwin wrote:
On Mon Jul 27/2009 @ 2:07:P -0500 asdasd, Jeff Ortel wrote:
All,
The pgsql branch has been merged to master. As most of you know, this
involves some changes in schema (source) directory structure, conventions
and development procedures. I'm working on a wiki page
All,
The 'chameleon' schema translation tool now available in Fedora updates for F-10 F-11.
Should be in EPEL (4,5) in a few weeks.
Regards,
Jeff
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
Jason,
You seeing this too?
On 08/12/2009 04:16 PM, Jason Dobies wrote:
I don't really know what purpose they serve and it's just a matter of
preference so if it's a major problem then no worries.
For what it's worth, I vote for having these cleaned up too. That, or
potentially built to a
On 08/14/2009 09:03 AM, Devan Goodwin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 14 Aug 2009 15:00:12 +0200
Michael Mrakamichael.mr...@redhat.com wrote:
Fedora Hosted Git Repositories - spacewalk.git/rss log:
% Add spacewalk-backend Requires on python-pgsql.
%
% Add
Very cool!
On 10/01/2009 12:40 PM, Greg DeKoenigsberg wrote:
So I did this little thing, and I'd like to know if other people find it
useful.
I just got a spiffy new laptop that does virt pretty well, and I'm
running F11 on it. Which gives a lot of neat virt stuff for free, that
makes the
43 matches
Mail list logo
