Re: Avoid overwritting other's data?
- From: "Bill Bach" <goldstar@xxxxxxxxxxxxx>
- Date: Sun, 06 Nov 2005 22:02:33 -0600
You could create the SQL statement to build the temp table into a
unique name, leveraging the user's connection ID or some other unique
value.
PSQLv9 has this feature in it with the EXECUTE statement, if you need
this capability within stored procedures.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach@xxxxxxxxxxxxxxxxxxxx
http://www.goldstarsoftware.com
*** Chicago: Pervasive.SQL Service & Support - November, 2005 ***
*** Chicago: Pervasive DataExchange Class - November, 2005 ***
DaleM@xxxxxxxxxxxxxx wrote:
> Hi All,
>
> How do I avoid overwritting other workstations' data in my own
> temporary tables? If two workstations are doing the following at the
> same time:
>
> SELECT * INTO TempTable1 FROM Table1
>
> Is there some way TempTable1 will only have my data? I've heard that
> Microsoft's SQL Server provides support for this using #TempTable1 and
> in similar cases ##TempTable1 where #TempTable1 is my own temporary
> table. How can I do something similar with Pervasive?
>
> Many thanks,
> Dale
.
- References:
- Avoid overwritting other's data?
- From: DaleM@xxxxxxxxxxxxxx
- Avoid overwritting other's data?
- Prev by Date: Re: Status 11 and 12 with PSQL 9.1
- Next by Date: Grouped view joins are not supported?
- Previous by thread: Avoid overwritting other's data?
- Next by thread: Grouped view joins are not supported?
- Index(es):