Is there a way in BackdropCMS to create a view pulling fields from two related (many-to-many (yes, via a third table)) tables in an external database (on the same server/domain)?
Maybe someone else knows of something out of the box that will do this, but I've not heard of it.
If you're looking for inspiration, you could look at the module above to see how easy it would be to implement in Backdrop, or the CiviCRM-Backdrop integration which allows Views on CiviCRM tables. By using relationships in the view, you can pull information from multiple tables in the external CiviCRM database. But to adapt that for your own custom use might be a big undertaking.
It has helped us access data in custom tables that are part of the same database for our Drupal 7 site. It has not been ported to Backdrop and I am unaware of any other Backdrop CMS solutions for this problem.
Thank you all for the various suggestions. I will test the Drupal modules (& check how/if I can convert them to Backdrop (if they work as required)) - otherwise the 'simple' solution seems to be using Modx Revolution instead.
What are you trying to accomplish, Egmund? There might be solutions, or workarounds, it depends on the use case. One idea: import the external content via the Feeds module, so that it becomes part of the Backdrop database.
I originally imported (yes, via 'feeds') two tables into Drupal 7, and that worked ok except I never figured out how to relate the two in Views so that I could pull fields from the related table into the view.
I (stupidly) converted to Drupal 8 (since converting to Backdrop failed utterly) and the tables got very messy - column names had to be cleaned and several columns deleted when exporting the tables for other use.
Now I am experimenting with the 'Data' module in D7 and at least it keeps my column names clean. But the module is immature and buggy - and I still need to figure out relationships in Views.
To clarify: I need a 'many-to-many' relationship between two tables (yes, via a third table). One could be 'users' and the other 'nodes', but I would prefer 'external' tables (but in the Backdrop/Drupal database).
@indigoxela - I agree, I mentioned the SVG topic specifically for the dev meeting. I think we'll definitely want Nate involved in that discussion. Good call!
Hi colbyat,
re display in the browser: the problem is that when a 500 occurs, this PHP process died before being able to render anything. So that won't work.
Logging is possible, but...
SVG's are a great topic for the design meeting, but also for the dev meeting.
Two currently active issues related to SVG overlap a bit when it comes to security aspects.
https://...
We might want to talk about this issue at the dev meeting (if someone is available to speak to the issue and what needs to be done):
Support SVG in Image Library
https://github.com/...
I know it's a long and difficult job to make Backdrop known and for people to realize the power (and simplicity) of the product. And I think you do a great job.
What I like about Backdrop...
Posted1 day 19 hours ago by Dominique (In Info Veritas) on:
Comments
I've never used it but maybe you could port the 7.x version of Views Database Connector?
Had hoped for a reason to 'stick with' Backdrop but - - - -
I will try the mentioned module in Drupal, but it is unlikely it will give me more than one table at a time/per view.
Maybe someone else knows of something out of the box that will do this, but I've not heard of it.
If you're looking for inspiration, you could look at the module above to see how easy it would be to implement in Backdrop, or the CiviCRM-Backdrop integration which allows Views on CiviCRM tables. By using relationships in the view, you can pull information from multiple tables in the external CiviCRM database. But to adapt that for your own custom use might be a big undertaking.
My team has used this Drupal 7 module before, but I have not used it much personally.
https://www.drupal.org/project/data
It has helped us access data in custom tables that are part of the same database for our Drupal 7 site. It has not been ported to Backdrop and I am unaware of any other Backdrop CMS solutions for this problem.
Thank you all for the various suggestions. I will test the Drupal modules (& check how/if I can convert them to Backdrop (if they work as required)) - otherwise the 'simple' solution seems to be using Modx Revolution instead.
What are you trying to accomplish, Egmund? There might be solutions, or workarounds, it depends on the use case. One idea: import the external content via the Feeds module, so that it becomes part of the Backdrop database.
Thank you Olaf for responding.
I originally imported (yes, via 'feeds') two tables into Drupal 7, and that worked ok except I never figured out how to relate the two in Views so that I could pull fields from the related table into the view.
I (stupidly) converted to Drupal 8 (since converting to Backdrop failed utterly) and the tables got very messy - column names had to be cleaned and several columns deleted when exporting the tables for other use.
Now I am experimenting with the 'Data' module in D7 and at least it keeps my column names clean. But the module is immature and buggy - and I still need to figure out relationships in Views.
To clarify: I need a 'many-to-many' relationship between two tables (yes, via a third table). One could be 'users' and the other 'nodes', but I would prefer 'external' tables (but in the Backdrop/Drupal database).