dolibarr-bugtrack
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Dolibarr-bugtrack] [Bug #799] Unknown column 'ff.facnumber' in 'field l


From: Doliforge
Subject: [Dolibarr-bugtrack] [Bug #799] Unknown column 'ff.facnumber' in 'field list'
Date: Wed, 17 Apr 2013 19:18:39 +0200

Doliforge
Is this email not displaying correctly?
update email preferences.

Unknown column 'ff.facnumber' in 'field list'

Latest modifications

2013-04-17 19:18 (Europe/Paris)
Changes:
  • Status: 
OpenClosed

Answer now

Snapshot

 Details
Submitted by:  David A. G. (braito) Submitted on:  2013-04-06 17:19
Last Modified On:  2013-04-17 16:25 Dolibarr version:  develop
PHP version:   Database type and version:  
OS Type/Version:   Category:  Core problem
Severity:  5 - Major 
Summary:   Unknown column 'ff.facnumber' in 'field list'
Description:  Dolibarr ha detectado un error técnico.
He aquí la información que podrá ayudar al diagnóstico:
Fecha: 20130406171302
Dolibarr: 3.4.0-alpha
Nivel de funciones: 0
PHP: 5.3.10-1ubuntu3.6
Server: Apache/2.2.22 (Ubuntu)

Url solicitada: /dolibarr/compta/bank/treso.php?account=1
Gestor de menú: eldy_menu.php

Tipo de gestor de base de datos: mysqli
Petición último acceso a la base de datos erróneo: SELECT 'invoice_supplier' as family, ff.rowid as objid, ff.facnumber as ref, (-1*ff.total_ttc) as total_ttc, ff.type, ff.date_lim_reglement as dlr, s.rowid as socid, s.nom, s.fournisseur FROM llx_facture_fourn as ff LEFT JOIN llx_societe as s ON ff.fk_soc = s.rowid WHERE ff.entity = 1 AND ff.paye = 0 AND fk_statut = 1 ORDER BY dlr ASC
Código devuelto último acceso a la base de datos erróneo: DB_ERROR_NOSUCHFIELD
Información sobre el último acceso a la base de datos erróneo: Unknown column 'ff.facnumber' in 'field list'
Step to reproduce bug:  
 Status
Resolution:  Fixed Assigned to:  Laurent Destailleur (eldy)
Status:  Closed 

Comments

HENRY Florian 2013-04-17 16:24
The bug has been corrected inside GIT sources
(http://www.github.com/Dolibarr/dolibarr).

So fix should be available with next stable release.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]