Pettis, Barry wrote:
So yes I use multiple databases. ( 4 of which are )
1. Lists all pats I manufacture ( includes general summary
information
like cycle time, number of process', number of critical process',
number
of metals used, etc... )
2. Lists all process steps at my site,
ght be worthwhile, will help in
making sure you are comparing apples to apples, oranges to oranges. Access is
not the best way to learn about databases as it has its own terminology that
does not translate well.
>
>
> -Original Message-
> From: Adrian Klaver [mailto:[EMAIL
On Tue, Apr 01, 2008 at 09:12:54AM -0600, Pettis, Barry wrote:
> I guess the biggest problem is trying to describe something in terms
> that all can understand. On a forum like this most "CONTRIBUTORS" those
> who answer questions speak a language that the typical novice poster
> doesn't use or un
derstand. So when the question is posed there is a
disconnect between poster and responder. So I'm hoping that I've been
able to adequately clear the air. If not it's always fun to try.
-Original Message-
From: Adrian Klaver [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 01, 200
On Monday 31 March 2008 4:20 am, Pettis, Barry wrote:
> Wow seems like this post took on a life of it's own. All I wanted to do
> was to be able to use a table that someone else has all ready created.
> Seems like somewhere someone mentioned a DBA ( which I'm assuming to be
> "Database Administrat
On Mon, Mar 31, 2008 at 05:20:56AM -0600, Pettis, Barry wrote:
> I wish I could say that I knew with certainty what schemas are or 2PC
> is. Would be nice if I had exposure to other databases as well. I'm
> sure that I'd have the same questions about MSft's SQL server.
Schemas are a subdivisio
e same questions about MSft's SQL server.
But I thank the forum here for all the input.
Regards,
Barry Pettis
CSO Atmel Corp
Project Tech
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Daniel Verite
Sent: Monday, March 31, 2008 3:36 AM
To: pg
> Also, 2PC is subject to unresolved transactions (or something like
that).
>
> > > Even in Oracle you don't have cross db queries.
> >
> > On the contrary you do. You can refer to objects in another
database by
> > [EMAIL PROTECTED], very useful to mix local and remote data
in no
> > time. DB
Scott Marlowe wrote:
> > Even in Oracle you don't have cross db queries.
>
> On the contrary you do. You can refer to objects in another
database by
> [EMAIL PROTECTED], very useful to mix local and remote data
in no
> time. DBLINK_NAME represents a connection to another databa
On Sat, Mar 29, 2008 at 4:53 PM, Daniel Verite <[EMAIL PROTECTED]> wrote:
> Scott Marlowe wrote:
>
> > How do you do cross db access within a transaction?
> > You can't, and it's not likely that any code will be put in place to
> do this.
>
> But wasn't such code announced in 8.1? From
Scott Marlowe wrote:
How do you do cross db access within a transaction?
You can't, and it's not likely that any code will be put in place to
do this.
But wasn't such code announced in 8.1? From
http://www.postgresql.org/about/news.422 :
"Two-Phase Commit (2PC): Long in demand for W
Oh, I also know about 2pc, but that's not quite done yet, and it's not
perfect either. When it's working then maybe someone could work on
cross-db queries through it.
But I'm not looking for that, 2pc has so many more interesting
applications than cross db queries.
--
Sent via pgsql-general mai
Let me further explain things. From the perspective of PostgreSQL,
all transactions occur within a single instance of a connection to a
single database.
When that connection is lost, any transactions roll back.
Transactional integrity is therefore only guaranteed during the
duration of a connecti
On Fri, Mar 28, 2008 at 8:44 PM, Brent Wood <[EMAIL PROTECTED]> wrote:
> I have mixed feelings,
>
> I agree that pretty much equivalent functionality CAN be delivered using
> schemas, but some RDBMS's do not have this restriction. Business cases &
> preferences do not necessarily follow database
Brent Wood wrote:
I am looking to convince a business which does not use schemas, but
does use separate databases to move to Postgres & having to shift
from this paradigm is an issue for them. They are perfectly entitled
to require such an approach, if we want to increase the user base of
Postgr
I have mixed feelings,
I agree that pretty much equivalent functionality CAN be delivered using
schemas, but some RDBMS's do not have this restriction. Business cases &
preferences do not necessarily follow database design preferences or
capabilities, so irrespective of whether a schema approac
On Thu, Mar 27, 2008 at 11:29 PM, Swaminathan Saikumar
<[EMAIL PROTECTED]> wrote:
> I am fairly new to Postgres. However, I have to say that I agree with
> Barry's comments.
The real problem here is that you are not using the db properly. You
should have one db with all these data in it in differ
On Thu, Mar 27, 2008 at 10:29:37PM -0700, Swaminathan Saikumar wrote:
> 4. Why not provide that feature as a core feature, rather than an add-on? If
> the community really feels strongly about this, discourage this practice
> with a best-practices section, citing problems with examples, and
> worka
I am fairly new to Postgres. However, I have to say that I agree with
Barry's comments.
The community's response is technically valid; they do talk about a better
way of 'designing' things, and what the company 'should' be doing.
However, coming from a MS-Sql world, people want multiple databases f
Em Thursday 27 March 2008 08:29:04 Pettis, Barry escreveu:
> An addon Being self schooled in databases to me this seems to be a
> kludge. If you work in a large company environment the odds that
> someone somewhere is all ready storing or collecting data that you need
> ( by this I mean base
Regards,
Barry Pettis
-Original Message-
From: Richard Huxton [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 27, 2008 3:45 AM
To: Pettis, Barry
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Using tables in other PostGreSQL database
Pettis, Barry wrote:
> Now this PostGreSQL
tis
-Original Message-
From: Richard Huxton [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 27, 2008 5:55 AM
To: Pettis, Barry
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Using tables in other PostGreSQL database
Pettis, Barry wrote:
> An addon Being self schooled in
Pettis, Barry wrote:
It sounds to me like you want to share a single database between
users,
possibly using a suitable mix of schemas and roles to apply suitable
permissions. If you don't want them to have shared access to the data
then you can have separate databases and grant them access onl
Pettis, Barry wrote:
An addon Being self schooled in databases to me this seems to be a
kludge.
Ah, well, self-schooling is always a good position from which to make
sweeping generalisations.
> If you work in a large company environment the odds that
someone somewhere is all ready sto
Pettis, Barry wrote:
Now this PostGreSQL "server" has many databases in it. Some of which I
have access to. I don't want to reinvent the wheel ( so to speak ) by
having to replicate the table in my database. Then having to create
routines that will extract from A to replicate in B. How do I r
I work at a fairly large company 2000 people just at my site alone.
I've been given access to a new database which will be used for source
data for some software that the company just purchased.
Now this PostGreSQL "server" has many databases in it. Some of which I
have access to. I don't want t
26 matches
Mail list logo
