SEO

#1 (**permalink**) 04-16-2008, 01:01 AM

> Eric and Tom: thank you very much for your help, I
> will try your suggestions tomorrow at work.
> The sql statements are issued from a COBOL program,
> which can also issue the same statements to other
> databases (MySQL, MS SQLServer), so the first thing Im
> going to do is trying to change the encoding setup,
> which would be the most homogeneous solution that
> wouldn't interfere with the other databases, that
> currently handle well those strings with hexadecimal
> data.
>
> Thank u very much again!
> Luciano.

Just curious: what COBOL vendor/compiler are you using?

Merlin

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

#2 (**permalink**) 04-16-2008, 01:01 AM

James M Doherty PGADMIN wrote:
> I am not sure you are aware but COBOL will cause
> brain damage if used for an extended period of time
>

Yep that is where all the Y2K stuff came from. People
had been using Cobol for too long to actually program
correctly

Don't even get me started on all the damage Java is doing
to once young, inspired and productive programmers.

Sincerely,

Joshua D. Drake

> Jim
> ----- Original Message ----- From: "Merlin Moncure"
> <merlin.moncure@rcsonline.com>
> To: "Luciano" <ldelio@yahoo.com>
> Cc: <pgsql-odbc@postgresql.org>
> Sent: Wednesday, January 12, 2005 9:33 AM
> Subject: Re: [ODBC] Query with hexadecimal characters
>
>> Eric and Tom: thank you very much for your help, I
>> will try your suggestions tomorrow at work.
>> The sql statements are issued from a COBOL program,
>> which can also issue the same statements to other
>> databases (MySQL, MS SQLServer), so the first thing Im
>> going to do is trying to change the encoding setup,
>> which would be the most homogeneous solution that
>> wouldn't interfere with the other databases, that
>> currently handle well those strings with hexadecimal
>> data.
>>
>> Thank u very much again!
>> Luciano.
>
>
> Just curious: what COBOL vendor/compiler are you using?
>
> Merlin
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html

--
Command Prompt, Inc., your source for PostgreSQL replication,
professional support, programming, managed services, shared
and dedicated hosting. Home of the Open Source Projects plPHP,
plPerlNG, pgManage, and pgPHPtoolkit.
Contact us now at: +1-503-667-4564 - http://www.commandprompt.com

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

#3 (**permalink**) 04-16-2008, 01:01 AM

At the moment we are using RM/Cobol, which is a
Liant's product. Some time ago we also used
Microfocus's Merant Cobol, which is quite much better,
but extremely expensive...

--- Merlin Moncure <merlin.moncure@rcsonline.com>
wrote:

> > Eric and Tom: thank you very much for your help, I
> > will try your suggestions tomorrow at work.
> > The sql statements are issued from a COBOL
> program,
> > which can also issue the same statements to other
> > databases (MySQL, MS SQLServer), so the first
> thing Im
> > going to do is trying to change the encoding
> setup,
> > which would be the most homogeneous solution that
> > wouldn't interfere with the other databases, that
> > currently handle well those strings with
> hexadecimal
> > data.
> >
> > Thank u very much again!
> > Luciano.
>
> Just curious: what COBOL vendor/compiler are you
> using?
>
> Merlin
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please
> send an appropriate
> subscribe-nomail command to
> majordomo@postgresql.org so that your
> message can get through to the mailing list
> cleanly
>

__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Re: Query with hexadecimal characters