[TYPO3-dev] current usage of DBAL, FYI: I gave up

[Steffen Ritter]

Hello Martin,
thanks for response.
If you mean with "toying around" that I'm just testing possibilities 
without using it for production envirement you are wrong. I really have 
to do a setup.

The background about is the following: Our network admins have an 
administration database where all users are listet, all their registered 
hosts with given ips an mac adresses. At all network joints clients have 
only access if there IP and their MAC are valid combination.
I just created such an auth-service for typo3 automatically login 
fe_users on, if their ip-mac combination is recognized. (added 
hoststable with irre to fe_users). For this I worked with imported data 
to my tables.

Network admins stated out, that this behavoiur is not "clean" enough, 
they do not want a copy of their database (which is mysql too). So we 
tried to figure out how to solve this problem... And thats the point 
where DBAL comes in.
It said it enables us to use some tables in another DB. So we connected 
the netadmin database over an ssl-tunnel to the webserver and connected 
it with dbal to typo3,build fe_users, fe_groups and the mac-table with 
views.
User import and editing worked fine, but we got the joining problems as 
mentioned, because all systables are somehow joined with each other 
(f.e. fe_groups and pages for access rules in frontend) and sohow should 
lie in one database.

After figuring out our possibilities, debugging dbal and the "get DB 
handler" feature and so on we decided that it is to much work to 
completely rewrite dbal to work with different databases and joins since 
we would have to start at zero. That's why, "I gave up" with dbal, it 
simply was not able to solve our problems.

At last, we i transferred the whole typo3 database from the mysql-server 
of the webserver to the netadmin (mysql-)server and configured typo3 to 
use this on port 3000-ssl-tunneled database natively.
The clue to this is: I can have a view, selecting data from another 
database on the same mysql server (which solves my problems). It's a 
little more slower than db on same server, but it should work.

I hope now it'S clear, what I wanted to state out.

kind Regards

Steffen

Martin Kutschker schrieb:
> Steffen Ritter schrieb:
>> Hello,
>> I just wanted to let you know that I gave up my DBAL tests.
>> With the patch mentioned and a useful configuration I could use 
>> fe_user and fe_group from another db (which I made typo3 redable by 
>> views).
>> BUT thats where the real big problems startet... There is no Editing 
>> in BE possible without joining und fe_groups and no page rendering 
>> without joining fe_sessions on fe_users and so on... In fact, 
>> systables on another db won't work.
> 
> So you're using the table mapping feauture where only specific tables 
> reside in another DB. While this is possible and was meant as a nice 
> idea, I don't think this is the common setup. Usually you want to have 
> either a different DB than Mysql (most request I see are for PostreSQL, 
> Oracle and MS SQL).
> 
> Of course using some tables from DB a and others from DB b won't work 
> with joins. This nifty feature is definitely a bit tricky to use as you 
> have to know in advance which tables will be joined where.
> 
> Steffen, I have no idea if you need DBAL or just toying around, but I 
> suggest those who are interested in DBAL should concentrate on the one 
> DB for all tables configuration.
> 
> Masi