Issue 1615044: Always check on delete restrict for issue1588

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line
<Enter> :	respond to / edit current comment
d :	mark current comment as done

	Issue
u :	up to list of issues
m :	publish + mail comments
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue
# :	close issue

	Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :	save comment
<Esc> :	cancel edit

Issue 1615044: Always check on delete restrict for issue1588 (Closed)

Can't Edit
Can't Publish+Mail
Start Review

Created:
15 years, 10 months ago by ced

Modified:
15 years, 10 months ago

Reviewers:
bch, yangoon1

Visibility:
Public.

Patch Set 1 #

Patch Set 2 : Fix cursor name #

Created: 15 years, 10 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+12 lines, -13 lines)			Patch
	M	trytond/model/modelsql.py	View	1	2 chunks	+12 lines, -13 lines	0 comments	Download

Messages

Total messages: 4

Expand All Messages | Collapse All Messages

yangoon1

Since you are requesting comments: Of course I don't like, as usually, to fix the ...

15 years, 10 months ago (2010-06-16 08:36:20 UTC) #3

ced

15 years, 10 months ago (2010-06-16 15:53:03 UTC) #4

On 2010/06/16 08:36:20, yangoon wrote:
> Since you are requesting comments:
> 
> Of course I don't like, as usually, to fix the error of one backend in the
> abstraction layer, thus moving the logic of the SQL-Layer, which should be
> provided by the RDBMS, into the framework as a whole. It should be fixed
> whenever possible in the backend. And if it cannot be fixed in the backend,
the
> use of such backends should be warned with a BIG FAT warning.
> 
> OTOH I have to admit, that I currently don't know, how much SQL-logic is
already
> in the framework...

Yes but this patch as also the advantage to give a more accurate error message.

Expand All Messages | Collapse All Messages