On Saturday 20 October 2001 08:53, you wrote:
> Andre,
>
> The only reason to have data for one query in different databases is if
> the databases are on different machines. If you're running on PC-type
> hardware, you might have to do that some times for performance reasons.
> But if at that poin
CREATE TABLE tablename (colname SERIAL);
okay, but how do I set the beginning number. So far the only thing I
have been able to do is directly after creating the serial column, I do:
select setval('tablename_colname_seq', 15753);
Is this the only way to set the beginning number of a sequence?
Bhuvan,
> How can we connect to different database using plpgsql function? Can
> we?
No, you can't.
-Josh
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Horst,
> There are many more good reasons to do so. Example from my own
> domain,
> medicine:
> Thus, we have multiple databases on multiple servers all depending on
> each
> other.
Your reasons all make sense. What you need is not inter-database
queries but a robust middleware layer, such a
Hi
I think most of you are missing the point here.
GUIDs are unique and they are required for Enterprise development.
For those of you who have used multi master replication on Oracle or MS
SQL, you know that identity columns and sequences are problematic. The
only way to work with primary key
On ðÔÎ, 2001-10-26 at 21:14, [EMAIL PROTECTED] wrote:
> Hi
>
> I think most of you are missing the point here.
>
I'm missing nothing :)
"uniqueidentifier" (128-bit unique value) data type fot PostgresSQL
exists and is used at least by me. It utilizes functionality of uuid
library from widely use
Folks,
> I think most of you are missing the point here.
>
> GUIDs are unique and they are required for Enterprise development.
I don't know. I have yet to hear a persuasive argument as to why none
of the schemes previously mentioned would not work. While a "GUID"
automated by the RDBMS pla
On Fri, 26 Oct 2001, Josh Berkus wrote:
> Horst,
>
> > There are many more good reasons to do so. Example from my own
> > domain,
> > medicine:
> > Thus, we have multiple databases on multiple servers all depending on
> > each
> > other.
>
> Your reasons all make sense. What you need is not
Hi
The overhead in generating GUIDs is minimal.
I've never heard of a GUID implementation that uses random numbers. In
most cases it is a functions of the date, a sequence, and/or the MAC.
Why would you want to use two columns when you use could one? Two
columns in each table would clutter your
"Kaiserdigital":
> Why would you want to use two columns when you use could one? Two
> columns in each table would clutter your scheme as well as your
> procedures.
It's a relational integrity issue. A GUID, by definition, contains two
pieces of information:
1. The local primary key
2. The serv
> Hi everybody,
> I was playing with psql and accidently deleted a couple of records from
> my database. I am wondering if there is any way to restore them. I know
> that in Oracle you can do 'rollback work' from SQLPlus interface and it
> would rollback all the updates done to the database.
That
On óÒÄ, 2001-10-24 at 09:55, Dinesh Parikh wrote:
> Hi,
> Is there any concept of sys_Guid in postgres.
> If yes what is that ??
> As i am using GUID in sql and oracle, then what is counterpart of this in postgres.
>It is urgent.
>
> Thanks in advance
> Bye
> Dinesh Parikh
>
Look at http://www
12 matches
Mail list logo
