QGIS Issue Tracking: Issueshttps://issues.qgis.org/https://issues.qgis.org/favicon.ico2019-05-24T06:08:29ZQGIS Issue Tracking
Redmine QGIS Application - Bug report #22134 (Open): Unable to copy selected rows from attibute table whi...https://issues.qgis.org/issues/221342019-05-24T06:08:29ZURIIT URIITkupr@uriit.ru
<p>While the “Dock Attribute Table” button is pressed, it is not possible to copy all selected lines in the attribute table using the “Ctrl + c” key combination.<br />After undocking the attribute table, everything works fine.</p>
<p><img src="https://issues.qgis.org/attachments/download/14979/1.png" alt="" /></p> QGIS Plugin Site - Bug report #22123 (Open): test 1https://issues.qgis.org/issues/221232019-05-22T12:50:42ZRichard Duivenvoorde
<p>test 1</p> QGIS Application - Feature request #22121 (Open): Sort inputs parameters in QGIS modelerhttps://issues.qgis.org/issues/221212019-05-22T10:12:55ZMaxime RIOUmaxime.riou@ymail.com
<p>This refers to a question on GIS Stack exchange (<a class="external" href="https://gis.stackexchange.com/questions/322831/sort-inputs-parameters-in-qgis-modeler">https://gis.stackexchange.com/questions/322831/sort-inputs-parameters-in-qgis-modeler</a>). <br />I created a model in QGIS 3.6 with three inputs parameters (two vector layer and one vector field). When I run the model, the inputs are not sorted in a correct way: the vector field is requested before the vector layer.</p>
<p>I searched on previous feature requests and I found this <a class="issue tracker-1 status-5 priority-5 priority- closed" href="https://issues.qgis.org/issues/11702" title="Support reordering the input fields in a Processing model GUI (Closed)">#11702</a> but it is closed now.</p>
<p>It would be nice to choose the order of the inputs parameters. For example, if the input parameters are sorted in alphabetical order, the user could name inputs "1_inputXX, 2_inputYY, etc.".</p>
<p>The proposed answer on GIS stackexchange is the following workaround :</p>
<p>Export Model as Python Algorithm to get a translated script of your model. Here you could order the parameters however you like in the <br /><pre>
initAlgorithm() function. E.g.:
def initAlgorithm(self, config=None):
self.addParameter(QgsProcessingParameterFeatureSource('1conduites', '1_Conduites', types=[QgsProcessing.TypeVectorLine], defaultValue=None))
self.addParameter(QgsProcessingParameterVectorLayer('2regard', '2_Regard', types=[QgsProcessing.TypeVectorPoint], defaultValue=None))
self.addParameter(QgsProcessingParameterFeatureSource('3idregard', '3_ID_regard', types=[QgsProcessing.TypeVector], defaultValue=None))
self.addParameter(QgsProcessingParameterFeatureSink('Result', 'result', type=QgsProcessing.TypeVectorPolygon, createByDefault=True, defaultValue=None))
</pre></p> QGIS Application - Bug report #22119 (Open): crashed when saving a few changeshttps://issues.qgis.org/issues/221192019-05-22T04:32:07ZAlonso Acunaacuna007@gmail.com
<a name="User-Feedback"></a>
<h2 >User Feedback<a href="#User-Feedback" class="wiki-anchor">¶</a></h2>
<p>crashed when saving a few changes</p>
<a name="Report-Details"></a>
<h2 >Report Details<a href="#Report-Details" class="wiki-anchor">¶</a></h2>
<p><strong>Crash ID</strong>: e3e9dc422a6d2f320711ed5f0a10ac180d98d1ed</p>
<p><strong>Stack Trace</strong><br /><pre>
memcmp :
VSICreateCachedFile :
SASetupDefaultHooks :
SHPReadObject :
SHPPartTypeName :
SHPPartTypeName :
wildcards :
QgsAbstractFeatureIterator::nextFeature :
QgsVectorLayerFeatureIterator::fetchFeature :
QgsAbstractFeatureIterator::nextFeature :
QgsVectorLayerLabelProvider::registerFeature :
QgsVectorLayerLabelProvider::registerFeature :
QgsMapRendererCustomPainterJob::doRender :
QgsMapRendererCustomPainterJob::staticRender :
QgsMapRendererJob::renderingTime :
QThreadPoolPrivate::reset :
QThread::start :
BaseThreadInitThunk :
RtlUserThreadStart :
</pre></p>
<p><strong>QGIS Info</strong><br />QGIS Version: 3.6.2-Noosa<br />QGIS code revision: <a class="changeset" href="https://issues.qgis.org/projects/qgis/repository/revisions/656500e0c4a7f044ae3b1678e8b512c33640207f" title="Release of 3.6.2">656500e0c4</a><br />Compiled against Qt: 5.11.2<br />Running against Qt: 5.11.2<br />Compiled against GDAL: 2.4.1<br />Running against GDAL: 2.4.1</p>
<p><strong>System Info</strong><br />CPU Type: x86_64<br />Kernel Type: winnt<br />Kernel Version: 6.3.9600</p> QGIS Application - Bug report #22087 (Open): GRASS Region Extent not shown in Batch Modehttps://issues.qgis.org/issues/220872019-05-15T16:22:49ZPedro Venânciopedrongvenancio@gmail.com
<p>When using Processing GRASS algorithms in batch mode, the GRASS_REGION_EXTENT_PARAMETER is not shown.</p>
<p>This happens in QGIS 3.4.7 and QGIS 3.6.2, but seems ok in 3.7 (master).</p>
<p>To reproduce:</p>
<p>1. Run a GRASS algorithm. For instance, v.to.rast. In 'Advanced parameters' you see "GRASS GIS 7 region extent (xmin, xmax, ymin, ymax) [optional]".<br />2. Run the same algorithm as Batch Process.<br />3. Toggle to advanced mode.<br />4. The "GRASS GIS 7 region extent (xmin, xmax, ymin, ymax)" column is not shown.</p> QGIS Application - Bug report #21986 (Open): Can not save data of type "array of characters (Stri...https://issues.qgis.org/issues/219862019-05-03T10:58:37ZMickaël CALLACmickael.callac@lannion-tregor.com
<p>Test environment:<br />QGis 3.4.7-1 (LTR)<br />database: spatiaLite</p>
<p>The error appears in the case of a layer connected to a base SpatiaLite (generated by ogr2ogr) and for an array type field characters. The field in QGis has been set as "value relational ", the option" Allow multiple selections "is checked.</p>
<p>The field in QGis has the following properties:</p>
<p>Type: QString<br />Identity type: StringList<br />This is a field of type "JSONSTRINGLIST" in the base spatiaLite<br />When saving this field, the following error appears: 2019-05-03T11: 39: 48<br />CRITICAL Layer name layer: Type 5 of the x attribute of the entity y is unknown.</p> QGIS Application - Bug report #21775 (Open): qgis crash when filtering a layer with an attachment...https://issues.qgis.org/issues/217752019-04-05T08:41:44ZSergii Brazhynenkosbrazhinenko@yahoo.com
<p><strong>qgis crash when filtering a layer with an attachment field</strong></p>
<p>Crash ID: f40bf397c5155333687146b59354eebf255adf60</p>
<p>Stack Trace<br /><pre>
QtPluginWidgetAdapter::~QtPluginWidgetAdapter :
WebCore::ImageDocument::imageElement :
WebCore::ImageDocument::imageElement :
WebCore::DocumentWriter::end :
QWebFrame::setUrl :
QgsExternalResourceWidget::loadDocument :
QMetaObject::activate :
QgsFileWidget::fileChanged :
QMetaObject::activate :
QLineEdit::qt_static_metacall :
QMetaObject::activate :
QWidgetLineControl::finishChange :
QWidgetLineControl::internalSetText :
QgsExternalResourceWidgetWrapper::setValue :
QgsEditorWidgetWrapper::setFeature :
QgsAttributeForm::resetValues :
QgsAttributeForm::setFeature :
QgsDualView::mFeatureList_currentEditSelectionChanged :
QMetaObject::activate :
QgsFeatureListView::currentEditSelectionChanged :
QgsFeatureListView::editSelectionChanged :
QMetaObject::activate :
QItemSelectionModel::emitSelectionChanged :
QItemSelectionModel::select :
QItemSelectionModel::select :
QgsFeatureListViewDelegate::~QgsFeatureListViewDelegate :
QMetaObject::activate :
QTimer::timerEvent :
QObject::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QEventDispatcherWin32::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QCoreApplicationPrivate::sendPostedEvents :
qt_plugin_query_metadata :
QEventDispatcherWin32::processEvents :
CallWindowProcW :
DispatchMessageW :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
QCoreApplication::exec :
main :
BaseThreadInitThunk :
RtlUserThreadStart :
QGIS Info
QGIS Version: 3.6.1-Noosa
QGIS code revision: 2468226bc9
Compiled against Qt: 5.11.2
Running against Qt: 5.11.2
Compiled against GDAL: 2.4.1
Running against GDAL: 2.4.1
System Info
CPU Type: x86_64
Kernel Type: winnt
Kernel Version: 10.0.17134
</pre></p> QGIS Application - Bug report #21673 (Open): Unable to add new features in QGIS for PostGIS table...https://issues.qgis.org/issues/216732019-03-25T17:45:02ZDavid Mancinidmancini@backroadmapbooks.com
<p>Last Friday I encountered a new error that I've never seen before. When editing a new PostGIS table in QGIS 3.6.0 I'm unable to save my edits as the 'gid' column auto populates it's value as NULL. This behaviour seems to occur when drawing a new spatial feature, as well as when copy and pasting new features from a separate shapefile without 'gid' column.</p>
<p>There error received is as follows.<br />Could not commit changes to layer tablename</p>
<p>Errors: ERROR: 1 feature(s) not added.</p>
<pre><code>Provider errors:<br /> PostGIS error while adding features: ERROR: null value in column "gid" violates not-null constraint<br /> DETAIL: Failing row contains (null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, 0106000020E6100000010000000103000000010000000400000060015885FD2F...).</code></pre>
<p>Looking into the database the table is using gid SERIAL PRIMARY KEY to define the "gid" column. I've tried dropping and re-adding the "gid" column, creating new tables, even manually creating a sequence and manually defining a new gid column as gid integer NOT NULL DEFAULT nextval('"sequencename"'::regclass) but no luck.</p>
<p>The strange thing is other tables within our PostgreSQL/PostGIS database do respond properly, providing the nextval('sequencename'::regclass) within the editor form and attribute table when creating new features or copy and pasting features in from another source.</p>
<p>I looked into our database and it is reporting itself as <br />PostgreSQL 9.4.19 on x86_64-unknown-linux-gnu, compiled by gcc (Debian 4.9.2-10+deb8u1) 4.9.2, 64-bit<br />POSTGIS="2.1.4 r12966" GEOS="3.4.2-CAPI-1.8.2 r3921" PROJ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL 1.10.1, released 2013/08/26" LIBXML="2.9.1" LIBJSON="UNKNOWN" TOPOLOGY RASTER</p>
<p>I suspect that the database may have recently been upgraded to this version 9.4.19 which maybe related to this new glitch. Older tables in our database seem to function properly, recreating those same database tables using new tablenames seems to run into this new glitch.</p>
<p>When searching online I came across an older ticket - Bug report <a class="issue tracker-1 status-1 priority-4 priority-" href="https://issues.qgis.org/issues/19564" title="PostgreSQL sequences not always used when adding feature (Open)">#19564</a> which seems to describe the same behaviour. As described in this post, tables that do function properly seem to identify the 'gid' column as a 'Text Edit' widget type, whereas the new tables that are broken seem to identify 'gid' column as a 'Range' widget type. Looking at the database both tables were created the same manner using gid SERIAL PRIMARY KEY. However, somehow QGIS is detecting a difference between these two tables.</p>
<p>This issues seems is not only limited to the latest QGIS 3.6.0, I also tried QGIS 2.18.21 and the results are the same (some older tables provide nextval('sequencename'::regclass) and newer tables remain NULL. Without the ability for the database to auto-increment a gid column using a sequence properly, it makes our database significantly harder to use within QGIS. This issue seems to be affecting more users so I decided to file a new issue to see if any others have been able to find a suitable solution.</p>
<p>I've attached some screenshots for your reference. It seems that either QGIS, the PostgreSQL database or the way in which SERIAL columns are being communicated from one to the other has somehow changed recently, but I'm not sure as to where the change exists or how to resolve the behaviour. I'm hoping someone with more knowledge of the inner workings of QGIS and the PostGIS layer management will have some more understanding of what is happening here. This is the strangest behaviour I have ever come across in my 10 years of working with PostgreSQL/PostGIS and I'm absolutely stumped.</p> QGIS Application - Bug report #21586 (Open): Windows and Processing Raster calculator pyqgis trou...https://issues.qgis.org/issues/215862019-03-14T15:00:13Zmatteo ghettamatteo.ghetta@gmail.com
<p>The bug seems to be related ONLY on Windows system. A small dataset in attach.</p>
<p>Briefly: it seems that when using the Processing Raster calculator in Windows via pyqgis, it is not possible to use raster(s) entire path(s). Only raster names loaded in the TOC are available.</p>
<p>To reproduce the error:</p>
<ul>
<li>load the attached `calculated` raster in the TOC</li>
<li>run this script (that uses gdal_proximity on the loaded raster and then the output of gdal_proximity is used in the raster calculator)</li>
</ul>
<pre>
param_proximity = {
'INPUT': QgsProject.instance().mapLayersByName('calculated')[0],
'BAND': 1,
'UNITS' : 0,
'OUTPUT': os.path.join(output, 'distance.tif')
}
proximity = processing.run("gdal:proximity", param_proximity)
param_calculated = {
'EXPRESSION':'{}@1 * {}'.format(proximity['OUTPUT'], formula),
'LAYERS': proximity['OUTPUT'],
'OUTPUT': os.path.join(output, 'calcolato.tif')
}
calculated = processing.run("qgis:rastercalculator", param_calculated)
iface.addRasterLayer(calculated['OUTPUT'], 'final')
</pre>
<p>This is working on Linux and on QGIS 3.4, 3.6 and master while is ALWAYS failing in Windows. To make it working on Windows some lines have to be added:</p>
<pre>
param_proximity = {
'INPUT': QgsProject.instance().mapLayersByName('calculated')[0],
'BAND': 1,
'UNITS' : 0,
'OUTPUT': os.path.join(output, 'distance.tif')
}
proximity = processing.run("gdal:proximity", param_proximity)
QgsProject.instance().addMapLayer(QgsRasterLayer(proximity['OUTPUT'], 'dummy'))
rl = QgsProject.instance().mapLayersByName('dummy')[0]
param_calculated = {
'EXPRESSION':'{}@1 * {}'.format(rl.name(), formula),
'LAYERS': rl.name(),
'OUTPUT': os.path.join(output, 'calcolato.tif')
}
calculated = processing.run("qgis:rastercalculator", param_calculated)
iface.addRasterLayer(calculated['OUTPUT'], 'final')
</pre>
<p>Fianlly, but still <b>extremely</b> important, with the same data the result is completely different. On Windows there are some super strange values (1.79769e+308 adn -1.79769e+308): some serious trouble with NODATA values?</p> QGIS Application - Bug report #21501 (Open): Distance matrix does not maintain data type and prec...https://issues.qgis.org/issues/215012019-03-06T15:20:18ZAndy Whyteandrew.g.whyte@gmail.com
<p>I have noticed that the distance matrix does not maintain precision or data type in InputID field created from the ID of the Input Point Layer to the tool.</p>
<p>This is an issue because it means I cannot join my result to an existing layer. The Target Point layer does not seem to do this.</p>
<p>For example the attached shapefile has an ID column (double, REAL, 20, P=0). When run through the distance matrix it inserts a decimal place. Additionally even if I use an integer ID field the output table will still not join to itself so it must be changing the type somehow to stop it from joining.</p>
<p>I am using QGIS 3.6</p> QGIS Application - Bug report #21382 (Open): Fails to build with SERVER_PLUGINS disabledhttps://issues.qgis.org/issues/213822019-02-26T04:25:01ZTom Palanthomas@palan.at
<p>The following cmake configuration fails to build:</p>
<p>cmake -G Ninja \<br /> -DCMAKE_VERBOSE_MAKEFILE=1 \<br /> -DCMAKE_INSTALL_PREFIX=/usr \<br /> -DBINDINGS_GLOBAL_INSTALL=TRUE \<br /> -DPEDANTIC=TRUE \<br /> -DSERVER_SKIP_ECW=TRUE \<br /> -DQGIS_CGIBIN_SUBDIR=/usr/lib/cgi-bin \<br /> -DWITH_APIDOC=TRUE \<br /> -DGENERATE_QHP=TRUE \<br /> -DWITH_CUSTOM_WIDGETS=FALSE \<br /> -DWITH_GLOBE=FALSE \<br /> -DWITH_SERVER=TRUE \<br /> -DWITH_SERVER_PLUGINS=FALSE \<br /> -DWITH_QWTPOLAR=FALSE \<br /> -DWITH_DESKTOP=FALSE \<br /> -DWITH_GUI=TRUE \<br /> -DDOXYGEN_ON_DEMAND=TRUE ..</p>
<p>with the error message:</p>
<p>[3019/4062] Linking CXX shared library output/lib/libqgis_server.so.3.4.5<br />FAILED: output/lib/libqgis_server.so.3.4.5 <br />: && ccache /usr/local/bin/c++ -fPIC -Wall -Wextra -Wno-long-long -Wformat-security -Wno-strict-aliasing -Wl,--no-undefined -shared -Wl,-soname,libqgis_server.so.3.4.5 -o output/lib/libqgis_server.so.3.4.5 src/server/CMakeFiles/qgis_server.dir/qgsbufferserverrequest.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsbufferserverresponse.cpp.o src/server/CMakeFiles/qgis_server.dir/qgscapabilitiescache.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsconfigcache.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsfcgiserverrequest.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsfcgiserverresponse.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsfilterresponsedecorator.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsfilterrestorer.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsrequesthandler.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsserver.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsserverparameters.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsserverexception.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsserverinterface.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsserverinterfaceimpl.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsserverlogger.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsserverprojectutils.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsserverrequest.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsserverresponse.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsserversettings.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsservice.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsservicenativeloader.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsserviceregistry.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsfeaturefilterprovidergroup.cpp.o src/server/CMakeFiles/qgis_server.dir/qgsfeaturefilter.cpp.o src/server/CMakeFiles/qgis_server.dir/moc_qgscapabilitiescache.cpp.o src/server/CMakeFiles/qgis_server.dir/moc_qgsconfigcache.cpp.o src/server/CMakeFiles/qgis_server.dir/moc_qgsserverlogger.cpp.o src/server/CMakeFiles/qgis_server.dir/moc_qgsserversettings.cpp.o src/server/CMakeFiles/qgis_server.dir/moc_qgsserverparameters.cpp.o -L/home/tom/projects/InfraGIS/QGIS-server/debian-package/woserverbindings/build/src/core -L/home/tom/projects/InfraGIS/QGIS-server/debian-package/woserverbindings/build/src/gui output/lib/libqgis_analysis.so.3.4.5 -lproj -lfcgi -lpq -lgdal -lqca-qt5 output/lib/libqgispython.so.3.4.5 output/lib/libqgis_core.so.3.4.5 -lqca-qt5 /usr/lib/x86_64-linux-gnu/libQt5Xml.so.5.7.1 /usr/lib/x86_64-linux-gnu/libQt5Svg.so.5.7.1 /usr/lib/x86_64-linux-gnu/libQt5PrintSupport.so.5.7.1 /usr/lib/x86_64-linux-gnu/libQt5WebKitWidgets.so.5.7.1 /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.7.1 /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.7.1 /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.7.1 /usr/lib/x86_64-linux-gnu/libQt5Network.so.5.7.1 /usr/lib/x86_64-linux-gnu/libQt5Sql.so.5.7.1 /usr/lib/x86_64-linux-gnu/libQt5Concurrent.so.5.7.1 -lqt5keychain -lproj -lgeos_c -lgdal -lspatialindex -lexpat -lsqlite3 -lspatialite -lzip /usr/lib/x86_64-linux-gnu/libQt5SerialPort.so.5.7.1 /usr/lib/x86_64-linux-gnu/libQt5Positioning.so.5.7.1 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.7.1 -lpython3.5m -lutil -Wl,-rpath,/home/tom/projects/InfraGIS/QGIS-server/debian-package/woserverbindings/build/src/core:/home/tom/projects/InfraGIS/QGIS-server/debian-package/woserverbindings/build/src/gui:/home/tom/projects/InfraGIS/QGIS-server/debian-package/woserverbindings/build/output/lib: && :<br />src/server/CMakeFiles/qgis_server.dir/qgsserverinterfaceimpl.cpp.o: In function `std::default_delete<QgsServerCacheManager>::operator()(QgsServerCacheManager*) const':<br />qgsserverinterfaceimpl.cpp:(.text._ZNKSt14default_deleteI21QgsServerCacheManagerEclEPS0_[_ZNKSt14default_deleteI21QgsServerCacheManagerEclEPS0_]+0x1e): undefined reference to `QgsServerCacheManager::~QgsServerCacheManager()'<br />collect2: error: ld returned 1 exit status</p> QGIS Application - Feature request #20994 (Open): Add a way to pass additional parameters to GDAL...https://issues.qgis.org/issues/209942019-01-14T09:31:43ZMatthias Treitlermatthias.treitler@gmail.com
<p>The GDAL tool "gdaldem color-relief" <a class="external" href="https://www.gdal.org/gdaldem.html#gdaldem_color_relief">https://www.gdal.org/gdaldem.html#gdaldem_color_relief</a> allows to pass the "-alpha" argument so that the output raster also contains the alpha band. The GDAL tools dialog show a input text box for additional creation options however it is not passed to the actual command, not matter what is inserted here.</p> QGIS Application - Bug report #20760 (Open): Edits in GeoJson datasources are not saved anymorehttps://issues.qgis.org/issues/207602018-12-09T22:08:01ZEhsan Aliverdiehsan.aliverdi@gmail.com
<p>I tested this issue in Qgis 3.4.0, 3.4.1, 3.4.2 in all the same issue<br />in our company we work with Geojson files in Qgis. When editing the attributes of an existing feature in Geojson layer, QGIS creates a temp layer and applies the changes on that new temp layer and never applies the changes on original layer. <br />this problem wasn't there in version 3.2.3</p> QGIS Application - Bug report #19564 (Open): PostgreSQL sequences not always used when adding fea...https://issues.qgis.org/issues/195642018-08-08T09:24:59ZNicolas Boisteaultnboisteault@3liz.com
<p>I have several PostgreSQL layers with no geometries. All have an 'id' column with serial type so they have a primay key and a sequence. When I add a feature, with some of these tables I have 'nextval('schema.id_seq'::regclass)' in the id field (which is the correct behavior) and with some others I have a NULL value.<br />I can't see <strong>no</strong> difference between the tables with the good behavior and the others.<br />I've also noticed that when I open the 'Attributes form' tab for wrong behavior tables the id field has 'Range' Widget Type proposed. For good behavior tables it is 'Text Edit' Widget Type.<br />Issue also occurs in QGIS 2.18.x and I have tested with 3 different Windows machines. Database is PostgreSQL 9.6 on Ubuntu 16.04.<br />I can give limited access to my database if needed.</p> QGIS Application - Bug report #18295 (Open): PostGIS Data Loads Extemely Slowhttps://issues.qgis.org/issues/182952018-03-01T15:35:18ZMickey Dietrich
<p>I have added data from PostGIS in Version 2.18 and the one data set loads in about 2 seconds. With the new 3.0 version, it takes 2 minutes to load that same data layer. All my data sets load really slow in Version 3.0. Not sure what the difference is from 2.18 to 3.0, but it has really caused problems with using the newer version, since we utilize the PostGIS database for accessing most all of our data. Is there something I am missing to make it load faster like in 2.18 or is there something behind the scenes causing this problem? Thanks, Mickey</p>