QGIS-expected_behavior_-_PostGIS_layers.txt

expectations for PostGIS layers - Steven Mizuno, 2008-02-28 08:05 PM

Download (2.48 KB)

 
1
2/24/2008 Steven Mizuno
2

    
3
Quantum GIS
4

    
5
documenting my expectations for Add PostGIS Layer - dialog and layer handling
6
(this is with respect to how QGIS is currently, before any changes I have worked up)
7
 
8
PostgreSQL object names (database, schema, table, column names, etc.) and data values have support for:
9
+	Uppercase characters and special characters (beyond 'a' to 'z', '0' to '9' and underscore) for object names 
10
+	Internationalization	at present not working very well on object names
11
+	ability to choose encoding (0.9.1 and earlier have a combobox list of encodings that is not present in HEAD, but appears to not do anything; HEAD now has Locale setting) This may be moot if internationalization is well implemented.
12

    
13
Number type handling
14
+	int2 (smallint)
15
+	int4 (int)
16
+	int8 (bigint)	at present, not working properly
17
+	float4
18
+	float8
19
+	numeric		at present, only as string
20
+	null values should be displayed blank or something like <null> rather than zero
21

    
22
Text type handling
23
+	character
24
+	character varying
25
+	text
26

    
27
other types?    (what is expected; haven't tested)
28

    
29
Array types	at present, gets Assertion and program exit - at least handle as strings
30

    
31
QGIS object id (primary key)
32
	int4		only one at present
33
	int8
34
	uuid
35
	text
36

    
37
Schema support
38

    
39
Catalog support		future
40

    
41
Error handling		at present, very little; and many silent failures
42
+	should display message box and possible actions to take on database error
43
+	ability to try to reconnect to database on loss of connection
44

    
45
Password for database connection
46
+	storage in QGIS settings	yes or no - at present, it is always stored - the toggle doesn't do anything
47
+	a Password dialog on a blank (not) stored password	not at present
48
+	storage in project file	yes or no - at present, always stored
49
+	on layer load from project - dialog to login on failed connection instead of failure to load
50

    
51
Properties/ Metadata tab shows more useful information
52
+	Length, Precision column show PostgreSQL internal sizing values which aren't useful to the average end user
53
+	indicate the primary key chosen
54
+	Editing Capabilities indicate what the loaded layer can do (privileges on the table ANDed with the layer type capabilities
55

    
56
User manual has better information on the layer capabilities and the database features that aren't supported (basically, all of the above in end user understandable language)
57

    
58
in Add PostGIS Layer the list of available tables should show only those the user has SELECT privileges on, at present all tables that have suitable geometry and index columns are shown
59