Forger
Dashboard
Get involved
Reviews
Overview
Ready for review
Work in progress
Needs action
Needs review
Needs verification
Needs rebase
Negative votes
Reviewed and verified
Ready to merge
Issues
Stale issues
Possible duplicates
By category
By month
Sprints
Overview
Initiatives
TYPO3 Core
Review board
Tools
Backports
ReST helper
Help
Search
Login
Esc
Words find the open ones, a number the issue and the change with it.
Search
Search words
Include closed
Reviews
6
Issues
2
Issue
#43470 SQL engine parse ERROR: Still content in clause after parsing!: near "; "
Closed
Review
43470 [BUGFIX] EXT:form - wrong attribute handling
Abandoned
Show
/
Hide
Filter
TYPO3 Version
6.0
2
Status
Closed
2
Assigned to
Find an assignee
Stefan Neufeind
1
Tracker
Bug
2
Target Version
Category
Database API (Doctrine DBAL)
1
Install Tool
1
PHP Version
2
Priority
Should have
2
Marked as
Activity
Author
Find an author
Stefan Neufeind
2
Tags
Created
Created from and to
Apply
Showing
1
–
2
of
2
Sort by
Relevance
Newest
Oldest
Recently updated
Least recently updated
Priority
Sort
#43471
dbal used on clean install using mysql
Minimal install from source + dummy with TYPO3 6.0 and using 1-2-3-installer. DBAL was automatically activated. Could it be that’s in the defaults now? Or activated during installation and not disabled again although mysql (native) is…
Bug
Closed
Stefan Neufeind
Install Tool
v6.0
10/30/13, 15:15
#43470
SQL engine parse ERROR: Still content in clause after parsing!: near "; "
(this occured when using dbal – but problem is in the sql-parser in core) How to reproduce: dbal activated installing “dam” Fails with exception > SQL engine parse ERROR: Still content in clause after parsing!: near “; “ thrown in…
Bug
Closed
Stefan Neufeind
Database API (Doctrine DBAL)
v6.0
10/02/18, 12:14
Stefan Neufeind