[GENERAL] Integration with MS Sql Server
Guys, We have an in-house application that absolutely has to run against MS Sql Server. We also have an application that doesn't, but that needs to integrate with that MSSQL database. I'm considering any options, including using application code as an integration point. I'd prefer to somehow mirror the MS SQL db in PostgreSQL, but not sure if that's possible. Anyone been faced with a similar situation? If so, how'd you resolve it? Thank you! John ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] Integration with MS Sql Server
On 10/3/05, Dann Corbit <[EMAIL PROTECTED]> wrote: > Using SQL*Server, and OLEDB or ODBC data source can be connected as a > linked server. Then, TSQL queries can go against PostgreSQL tables as > though they were ordinary SQL*Server tables (but they have 4 part names > instead of 3 part names). Unfortunately, mirroring PostgreSQL within MS SQL Server is not an option in our case...we need to do it the other way around. Interesting info nonetheless...thanks. Is there no other way? John ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[GENERAL] PostgreSQL's bug tracker
Guys, I was interested in researching a few items regarding bug reports in PostgreSQL, but I can't seem to find what the project uses as a bug tracker. I see the web form and mailing list, but I can't imagine they're not captured in some central repository. Could someone point me in the right direction? Thanks! John ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] PostgreSQL's bug tracker
On 10/10/05, Tom Lane <[EMAIL PROTECTED]> wrote: > Old-timers will recall that we already had one bad experience with an > early open-source bug tracker, which has left people a bit shy of the > concept too. I think a large part of that had to do with confusion > between the purposes of bug *reporting* and bug *tracking*. A mailing > list does very well for reporting issues that might be bugs, but not so > well for tracking the status of acknowledged bugs. This "tracking" feature is crucial for us. We're working towards a large scale deployment of PostgreSQL across our enterprise, but not having an easy way to get the status of all reported bugs against our particular version isn't very comforting. Having a bug tracker in place would make life much easier, and my advocacy job much less trying. I sincerely hope the team will consider using one...bugtraq is fine, so is trac...just as long as one is in place. Thanks, JB ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[GENERAL] Stripping empty space from all fields in a table?
Guys,I have a table that has various fields that have whitespace in the values. I'd like to roll through and strip the left and right whitespace out of all fields that contain strings.Is there any easy way to do this? Thanks!JB
Re: [GENERAL] Stripping empty space from all fields in a table?
Worked perfectly...thank you!
Re: [GENERAL] Well, Pervasive is now out....
On 8/3/06, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote: Let's believe that that was the real reason... :-) If not, what was? Is this really a commentary on how many "enterprise"-y types are using Postgres? ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
