In the teleconference yesterday I suggested converting VARCHAR2 usage in
Oracle schema to VARCHAR as well. But the Oracle 11g docs seem to suggest
otherwise:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/sql_elements001.htm#sthref77
They keep saying VARCHAR _will_ be treated diff
bruce wrote:
> I talked to the Orafce author. He says Orace is focused on adding
> missing Oracle functionality to Postgres, rather than helping in
> porting.
>
> For example, decode() was only added in Orafce 3.0beta because Postgres
> already has the CASE statement. Also, NVL is COALESCE:
>
>
I talked to the Orafce author. He says Orace is focused on adding
missing Oracle functionality to Postgres, rather than helping in
porting.
For example, decode() was only added in Orafce 3.0beta because Postgres
already has the CASE statement. Also, NVL is COALESCE:
http://forums.devsh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 30 Jan 2009 02:18:51 +0530
Gurjeet Singh wrote:
> 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 29 Jan 2009 21:57:10 +0100
Jan Pazdziora wrote:
> On Thu, Jan 29, 2009 at 04:01:40PM -0400, Devan Goodwin wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Working on the population of PostgreSQL schema in
> > spacewalk-se
On Thu, Jan 29, 2009 at 04:01:40PM -0400, Devan Goodwin wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Working on the population of PostgreSQL schema in
> spacewalk-setup I landed in rhn-populate-database.pl, got the
> script ready to populate pgsql schema as well but even if the
> s
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 . "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Working on the population of PostgreSQL schema in
spacewalk-setup I landed in rhn-populate-database.pl, got the
script ready to populate pgsql schema as well but even if the
schema population fails miserably, the psql executable returns a
0 success cod
On Thursday 29 January 2009 09:12:07 am Miroslav Suchý wrote:
> Dennis Gilmore wrote:
> > All but 2 packages in git are built for fedora.
>
> I changed
> rel-eng/build-missing-builds-in-koji.sh
> so it now automatically builds all tagged packages in tag
> dist-f10-sw-0.5-candidate as well.
>
> De
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Added a start on the PostgreSQL schema layout in the pgsql branch and
some dummy tables/procedures. (will remove these as soon as there's
*any* real schema in play)
cd schema/spacewalk/postgresql/
psql -f main.sql -d spacewalk
For the record I've bee
Dennis Gilmore wrote:
Dennis is the F-10 repo available on koji for rsync too? What is the
url? I would like to add it to public nightly repo as well.
Hi Miroslav,
thanks in advance its at rsync://koji.rhndev.redhat.com/spacewalk/spacewalk-
f10/spacewalk-f10-0.5/
it update at the same times a
On Thursday 29 January 2009 09:12:07 am Miroslav Suchý wrote:
> Dennis Gilmore wrote:
> > All but 2 packages in git are built for fedora.
>
> I changed
> rel-eng/build-missing-builds-in-koji.sh
> so it now automatically builds all tagged packages in tag
> dist-f10-sw-0.5-candidate as well.
>
> De
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 29 Jan 2009 21:00:06 +0530
Gurjeet Singh wrote:
> Can you post the exact error message you got?
Not really an error so much as my code tries to call the procedure but
I have no PostgreSQL schema or procedures yet. :)
The ora2pg generated s
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 n
Dennis Gilmore wrote:
All but 2 packages in git are built for fedora.
I changed
rel-eng/build-missing-builds-in-koji.sh
so it now automatically builds all tagged packages in tag
dist-f10-sw-0.5-candidate as well.
Dennis is the F-10 repo available on koji for rsync too? What is the
url? I w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As mentioned in phone call this morning, a couple early requests for
PostgreSQL schema + procs to be ported, I ran into a need for these
in spacewalk-setup:
Stored procedure: create_first_org.sql
It delves out into a few tables, hopefully not far and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 29 Jan 2009 08:59:58 -0500
"Jesus M. Rodriguez" wrote:
>
> Let's be careful how we add to that document. We want the document to
> be accurate but as simple as possible. I don't like it when we have a
> bunch of conditionals in a howto, make
On Thu, Jan 29, 2009 at 8:14 AM, Devan Goodwin wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, 29 Jan 2009 16:04:34 +0530
> Vikram Rai wrote:
>
>> Hi,
>>
>> We have put together a document for deploying the Spacewalk dev
>> environment on CentOS 5.
>> There were a couple of s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 29 Jan 2009 12:19:26 +0100
Miroslav Suchý wrote:
> Dennis Gilmore wrote:
> > All but 2 packages in git are built for fedora.
> Good. Thx.
>
> > Please when you build build for F-10 also. instructions are
> > https://fedorahosted.org/spacew
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 29 Jan 2009 16:04:34 +0530
Vikram Rai wrote:
> Hi,
>
> We have put together a document for deploying the Spacewalk dev
> environment on CentOS 5.
> There were a couple of steps that we had to do in order to make it
> working on our local mac
Dennis Gilmore wrote:
All but 2 packages in git are built for fedora.
Good. Thx.
Please when you build build for F-10 also. instructions are
https://fedorahosted.org/spacewalk/wiki/ReleaseProcess
It wil be nice to have some target in Makefile.git (and/or build.py) to
build in both tags a
% > > jabberpy and perl-Filesys-Df are both in fedora and EPEL, I plan to
% > > remove them from spacewalk git tomorrow afternoon. please yell if you
think
% > > they should be kept. ive already blocked them from being built in
% > > spacewalk koji.
% > >
% > > Dennis
% > perl-Set-Crontab
% > p
Hi,
We have put together a document for deploying the Spacewalk dev environment
on CentOS 5.
There were a couple of steps that we had to do in order to make it working
on our local machines.
Please go through the attached document and let us know if the document
seems ok.
We had a suggestion to p
23 matches
Mail list logo
