Mark Forums Read

Proper multi-users design

Go Back

comp.databases.theory comp.databases.theory

Reply

Page 3 of 3

3

#21

Old

David BL

Posts: n/a

Re: Proper multi-users design - 10-16-2008 , 06:35 AM

On Oct 15, 8:38*pm, Ael <a... (AT) adnx (DOT) net> wrote:

Quote:

Hello,

I've inherited a single user application using a database (multiple
backends : Postgres, Firebird, Oracle) and need to bring it on par for
multi-users access.

Right now each DB operation (fetch a structure, update a record, ...) is
embedded in its own transaction, and I'm not really sure where to begin.

I'm not really looking for a specific DBMS procedure (that I can figure out
myself), but more for a generic best practices/how-to implementing proper
multi-users access.

I've searched a bit, but apart from the generic optimistic/pessim. locking
mechanisms available and transaction isolation did not find anything
worthwhile. Is my best bet to rework everything to _really_ use
transactions ?

Do you have any links, articles or books to recommend ?

Thanks in advance,

--
Ael

Is distributed atomicity of updates required? Avoid that if you can.

Reply With Quote

#22

Old

David BL

Posts: n/a

Re: Proper multi-users design - 10-16-2008 , 06:35 AM

On Oct 15, 8:38*pm, Ael <a... (AT) adnx (DOT) net> wrote:

Quote:

Hello,

I've inherited a single user application using a database (multiple
backends : Postgres, Firebird, Oracle) and need to bring it on par for
multi-users access.

Right now each DB operation (fetch a structure, update a record, ...) is
embedded in its own transaction, and I'm not really sure where to begin.

I'm not really looking for a specific DBMS procedure (that I can figure out
myself), but more for a generic best practices/how-to implementing proper
multi-users access.

I've searched a bit, but apart from the generic optimistic/pessim. locking
mechanisms available and transaction isolation did not find anything
worthwhile. Is my best bet to rework everything to _really_ use
transactions ?

Do you have any links, articles or books to recommend ?

Thanks in advance,

--
Ael

Is distributed atomicity of updates required? Avoid that if you can.

Reply With Quote

#23

Old

David BL

Posts: n/a

Re: Proper multi-users design - 10-16-2008 , 06:35 AM

On Oct 15, 8:38*pm, Ael <a... (AT) adnx (DOT) net> wrote:

Quote:

Hello,

I've inherited a single user application using a database (multiple
backends : Postgres, Firebird, Oracle) and need to bring it on par for
multi-users access.

Right now each DB operation (fetch a structure, update a record, ...) is
embedded in its own transaction, and I'm not really sure where to begin.

I'm not really looking for a specific DBMS procedure (that I can figure out
myself), but more for a generic best practices/how-to implementing proper
multi-users access.

I've searched a bit, but apart from the generic optimistic/pessim. locking
mechanisms available and transaction isolation did not find anything
worthwhile. Is my best bet to rework everything to _really_ use
transactions ?

Do you have any links, articles or books to recommend ?

Thanks in advance,

--
Ael

Is distributed atomicity of updates required? Avoid that if you can.

Reply With Quote

#24

Old

David BL

Posts: n/a

Re: Proper multi-users design - 10-16-2008 , 06:35 AM

On Oct 15, 8:38*pm, Ael <a... (AT) adnx (DOT) net> wrote:

Quote:

Hello,

I've inherited a single user application using a database (multiple
backends : Postgres, Firebird, Oracle) and need to bring it on par for
multi-users access.

Right now each DB operation (fetch a structure, update a record, ...) is
embedded in its own transaction, and I'm not really sure where to begin.

I'm not really looking for a specific DBMS procedure (that I can figure out
myself), but more for a generic best practices/how-to implementing proper
multi-users access.

I've searched a bit, but apart from the generic optimistic/pessim. locking
mechanisms available and transaction isolation did not find anything
worthwhile. Is my best bet to rework everything to _really_ use
transactions ?

Do you have any links, articles or books to recommend ?

Thanks in advance,

--
Ael

Is distributed atomicity of updates required? Avoid that if you can.

Reply With Quote

#25

Old

David BL

Posts: n/a

Re: Proper multi-users design - 10-16-2008 , 06:35 AM

On Oct 15, 8:38*pm, Ael <a... (AT) adnx (DOT) net> wrote:

Quote:

Hello,

I've inherited a single user application using a database (multiple
backends : Postgres, Firebird, Oracle) and need to bring it on par for
multi-users access.

Right now each DB operation (fetch a structure, update a record, ...) is
embedded in its own transaction, and I'm not really sure where to begin.

I'm not really looking for a specific DBMS procedure (that I can figure out
myself), but more for a generic best practices/how-to implementing proper
multi-users access.

I've searched a bit, but apart from the generic optimistic/pessim. locking
mechanisms available and transaction isolation did not find anything
worthwhile. Is my best bet to rework everything to _really_ use
transactions ?

Do you have any links, articles or books to recommend ?

Thanks in advance,

--
Ael

Is distributed atomicity of updates required? Avoid that if you can.

Reply With Quote

#26

Old

David BL

Posts: n/a

Re: Proper multi-users design - 10-16-2008 , 06:35 AM

On Oct 15, 8:38*pm, Ael <a... (AT) adnx (DOT) net> wrote:

Quote:

Hello,

I've inherited a single user application using a database (multiple
backends : Postgres, Firebird, Oracle) and need to bring it on par for
multi-users access.

Right now each DB operation (fetch a structure, update a record, ...) is
embedded in its own transaction, and I'm not really sure where to begin.

I'm not really looking for a specific DBMS procedure (that I can figure out
myself), but more for a generic best practices/how-to implementing proper
multi-users access.

I've searched a bit, but apart from the generic optimistic/pessim. locking
mechanisms available and transaction isolation did not find anything
worthwhile. Is my best bet to rework everything to _really_ use
transactions ?

Do you have any links, articles or books to recommend ?

Thanks in advance,

--
Ael

Is distributed atomicity of updates required? Avoid that if you can.

Reply With Quote

#27

Old

David BL

Posts: n/a

Re: Proper multi-users design - 10-16-2008 , 06:35 AM

On Oct 15, 8:38*pm, Ael <a... (AT) adnx (DOT) net> wrote:

Quote:

Hello,

I've inherited a single user application using a database (multiple
backends : Postgres, Firebird, Oracle) and need to bring it on par for
multi-users access.

Right now each DB operation (fetch a structure, update a record, ...) is
embedded in its own transaction, and I'm not really sure where to begin.

I'm not really looking for a specific DBMS procedure (that I can figure out
myself), but more for a generic best practices/how-to implementing proper
multi-users access.

I've searched a bit, but apart from the generic optimistic/pessim. locking
mechanisms available and transaction isolation did not find anything
worthwhile. Is my best bet to rework everything to _really_ use
transactions ?

Do you have any links, articles or books to recommend ?

Thanks in advance,

--
Ael

Is distributed atomicity of updates required? Avoid that if you can.

Reply With Quote

#28

Old

David BL

Posts: n/a

Re: Proper multi-users design - 10-16-2008 , 06:35 AM

On Oct 15, 8:38*pm, Ael <a... (AT) adnx (DOT) net> wrote:

Quote:

Hello,

I've inherited a single user application using a database (multiple
backends : Postgres, Firebird, Oracle) and need to bring it on par for
multi-users access.

Right now each DB operation (fetch a structure, update a record, ...) is
embedded in its own transaction, and I'm not really sure where to begin.

I'm not really looking for a specific DBMS procedure (that I can figure out
myself), but more for a generic best practices/how-to implementing proper
multi-users access.

I've searched a bit, but apart from the generic optimistic/pessim. locking
mechanisms available and transaction isolation did not find anything
worthwhile. Is my best bet to rework everything to _really_ use
transactions ?

Do you have any links, articles or books to recommend ?

Thanks in advance,

--
Ael

Is distributed atomicity of updates required? Avoid that if you can.

Reply With Quote

Reply

Page 3 of 3

3

« Previous Thread | Next Thread »

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

Posting Rules
You may not post new threads You may not post replies You may not post attachments You may not edit your posts vB code is On Smilies are On [IMG] code is On HTML code is Off

Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.