Drupal module development, custom database tables, pages for managing those data - module

I'm completely new to Drupal development
I want to learn how to create basic module with such functionality:
Create module with custom database tables
Create one or several new pages as logical section of the site
Manage data from database tables on those newly created pages
For example, I want to create subscription service with clients database
and manage their data (edit clients, export, change their status, etc...)
I want to do this on new pages on my site (not in admin section)
site.com/clients - list of client
site.com/client - client detailed info
etc
Please, provide some thoughts or tutorials (but not a ready module :) )

You can follow this tutorial for the basics in creating a D7 module.
https://www.drupal.org/node/1074360
As far as custom database tables I suggest taking a look at this module.
https://www.drupal.org/project/eck
Also take a look at this video for more info about 'ECK'.
http://codekarate.com/daily-dose-of-drupal/drupal-7-entity-construction-kit

Related

Database architecture for asp.net mvc websites builder system

I want to create the design of a SQL database that will hold the data entered from a dynamic created websites (something like http://www.wufoo.com).
Users of the system will create forms by dragging controls into the form and then they will use the created forms to build a website by including the forms in some pages.
What would be the options that I have when I create the architecture of the database.
Since you do not know what you will get in your DB, how the object will look like; I would suggest using NoSql.
Otherwise you need to create some very abstract table, let's say Form, and then make in inheritable by other tables (ye, you can do that in EF)

Vaadin integration of existing database

Hi I'm trying to implement a class dbHelper to create a connection to an existing database on the phpmyadmin site.
I want to read and edit entries in the database. So my question is, how you would recommend to implement this in vaadin.
You're looking to create an application that supports create, read, update and delete (an acronym CRUD), which are the four basic functions of persistent storage.
Tutorials for creating CRUD applications with Vaadin has been done quite a few times. The article Creating CRUD UI with Vaadin as well as Spring Data JPA CRUD with Vaadin git repository provide a good step-by-step instructional. As #Andre recommended, using JPAContainers and Bean Item Containers are going to cut down the amount of code you need to write, so it would be worth your time planning your data models accordingly. If you have any specific questions on accessing data with JPA, or anything else please let me know!

create databases and tables dynamically with Yii framework possible?

I am developing a system with a master database and multiple databases, once for each client. The client database and its tables will be created when the client fills in and submit a form with all the required details.
My question: does the Yii framework support the dynamic creation of databases and tables? If so, is there any example code? (I'm still learning about Yii) I couldnt find an answer on the Yii website (documentation and forum) nor on this site. (I did notice that dynamic databse connections are possibble with Yii - Yii Dynamic DB Connection according to user?)
For connections in runtime read php-yii-database-connect-in-runtime and after that, Yii have all Building Schema Manipulation Queries like CREATE, ALTER, DROP etc.
So easy and simple.
building-schema-manipulation-queries

Creating SAS BI Dashboard accounts for people outside our organization?

our organization has been using SAS BI Dashboard for several months now for internal use within our own organization. Now, we are working on a project where roughly 100 people in other, outside organizations will need to log on to our BI Dashboard site to view an individualized dashboard for their organization. We plan to use row-level permissions in an Information Map to control who is allowed to see what in terms of the data behind the dashboard indicators.
How would you recommend creating roughly 100 individual log-ons for outside users?
Is there a way to automate the process rather than manually creating all the accounts?
If I create the log-on name and password for each outside user, how/where would I store that in Management Console?
Any help would be appreciated - our office is small enough that we do not have a dedicated IT person or fully-trained SAS administrator, so I'm in over my head. Thanks!
As an ex SAS consultant, I can tell you briefly how I have solved this problem.
First, creating the users in batch should be easy. There are tons of scripts out there that will teach you this. I would recommend to create them in your LDAP server (probably Active Directory), to have them in a central place. That way, you can treat them the same way as you do the internal users.
To get them into the metadataserver, you should take a look at the macros that SAS provides for this:
The following macros are the core components used to import and synchronize user accounts from Active Directory to SAS metadata: %MDUIMPC , %MDUIMPLB , %MDUEXTR , %MDUCMP , %MDUCHGV , %MDUCHGLB. They are located in the following directory: [SAS Home]\SASFoundation\9.3\core\sasmacro.
This SGF proceeding will give you a practical description of the process:
http://support.sas.com/resources/papers/proceedings12/377-2012.pdf
As for the question you did not ask, "how to present the BI Dashboard webapplication to the external users". You need to set up a reverse proxy web server in a secure zone (DMZ). See this document for details: http://support.sas.com/resources/thirdpartysupport/v92m3/appservers/ApacheProxyJBoss.pdf
Hope this helps!
Stig

New to sharepoint development, do lists replace your database?

We're just starting Sharepoint development, and one of my first tasks is to build a data collection tool. It will be used across multiple sites, so there will be an admin area, and each site will pull in it's related questions, and record the data. I've gone through a bunch of tutorials on development, and have a fairly good idea of how to start. I just want to make sure I understand one thing. Do lists basically take the place of your database? If this was a regular app, I would create a question table, a link table that tells which questions are connected to which site, a table that stores the answer, linking to the site and question table.
Is this the basic pattern you follow, or should I be doing things differently for Sharepoint applications?
If the thought is to use an external databse, can anyone point me to some info on this?
In our Sharepoint project we stared with Lists. It was good to some point - till DB had only few relations between data. After adding tables and relations performance falls a lot and we had to switch to use standard DB in MS SQL Server. So I recomend to use DB.
Disadventages: you cannot use sharepoint controls to edit/view data and cannot restrict access to data from sharepoint level
Adventages: much faster access to data