Project

General

Profile

Actions

Bug #26856

closed

parseFromTables() in class.t3lib_sqlparser.php fails with "schema.table" definitions as usual for PostgreSQL

Added by Mungan over 13 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Backend API
Target version:
Start date:
2011-05-17
Due date:
2011-05-17
% Done:

0%

Estimated time:
0.00 h
TYPO3 Version:
4.5
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Many extension writers make use of Typo3 parsing function

parseFromTables() in

class.t3lib_sqlparser.php

and whereever this function is in use it is unable to pass
schema qualified table names.

Reason for this is the "." that needs to be respected.

So BUGFIX could be to change the regular expression in the following line 984 as
follows:

if ($stack[$pnt]['table'] = $this->nextPart($parseString, '^([[:alnum:]_.]+)(,|[[:space:]]+)')) {

I think this is quite severe for any PostgreSQL users out there
using the 4.5 Long Term Support.

Please put something like this line into the trunk.

Actions #1

Updated by Oliver Hader over 13 years ago

  • Target version changed from 4.5.3 to 4.5.4
Actions #2

Updated by Oliver Hader over 13 years ago

  • Target version changed from 4.5.4 to 4.5.6
Actions #3

Updated by Andreas Wolf about 13 years ago

  • Status changed from New to Needs Feedback

Doesn't this belong to DBAL rather than Backend API?

Actions #4

Updated by Chris topher about 13 years ago

  • Target version changed from 4.5.6 to 4.5.8
Actions #5

Updated by Ernesto Baschny almost 13 years ago

  • Target version changed from 4.5.8 to 4.5.12
Actions #6

Updated by Mungan over 12 years ago

I recently upgraded to Typo3 4.5.14 and this bug is still in!
Please clearify who can change this single line:

if ($stack[$pnt]['table'] = $this->nextPart($parseString, '^([[:alnum:]_.]+)(,|[[:space:]]+)')) {

in class.t3lib_sqlparser.php, function parseFromTables()

Please note, that this time I added [[]] around ':space:'
- I guess this is due to the fact, that PHP version has changed.

Thanks!

Actions #7

Updated by Alexander Opitz about 11 years ago

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?

Actions #8

Updated by Markus Klein almost 11 years ago

  • Status changed from Needs Feedback to Closed
  • Is Regression set to No

No feedback in the last 90 days => closing this ticket.

If you experience this issue again, please open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF