Database
This is a working group for those involved in the development and extension of Drupal's Next Generation database abstraction layer, including the Schema API and the development of new database drivers.
Please remember to read the documentation for the Database API. It will likely be helpful to review the PDO documentation as well.
Using information from another database for drupal user management
Hi
I was wondering is there a way to make use of information on another database to create user accounts.
I have a database with all my clients information already stored and I want to avoid duplicating the information on my Drupal database and I also want to take advantage of all the funtionality already available with Drupal user management.
All ideas and suggestions are welcome.
Thank you all for your time
T
What to do with slaves?
So this conversation hasn't happened yet, but it really really needs to. We have this nice and shiny new slave server support in Drupal 7, but we are not using it. That means we need to go through and flag which queries are "Slave safe", that is, are able to use a slave server if one is available without breaking stuff.
Oracle Driver for 7.x
Hi all,
i'm happy to say that today i closed the last odd test cases (http://drupal.org/node/464514), and that the 7.x driver for oracle looks working.
It would be very nice if someone wants to help with it to make it work even better / faster. My poor PHP skills makes the code ugly probably, and may be some of you can contribute some ideas to support a wider variety of SQL statements or to remove/improve some Regular Expressions.
The actual state is pretty difficult to explain because i worked on the driver almost for the last year in "free time" so excuse me if do not remember all the points. I'll use this post as a T.O.C. http://drupal.org/node/39260#comment-1124563:
Oracle support and O.R.M.
Hi all,
i'am one of the guys who is triyng to build an oracle driver for drupal.... (http://drupal.org/project/oracle)
I actually wrote 2 drivers: 1 for the 6.x and 1 for the 7.x. Both based on PDO_OCI, and both working pretty
well with the core, (i'am still working on the 7.x SimpleTest test cases but 90% is ok).
I started using the 6.x driver in production on February (when it was on sourceforge.net as drupaloracle).
A couple of days a go, one of my company web developers, told me:
"Hey.. we should use this X module.... It is cool!"
Multi-master synchronous replication system for MySQL on AWS with Drupal as POC
At MySQLcon I ran into the guys from Codership. They did a 25 minute presentation on how to do multi-master synchronous replication across many instances of MySQL.
In layman's terms.
If you are running 5 Master MySQL databases behind your giant Drupal site, and one of those servers crashes, you won't lose a transaction, and you won't corrupt your logs and destroy your database.
Development Job to make our database user-friendly. | PESI-SNM at Copenhagen University
We need assistance for our search-facility situated in a bit buggy database. We need to make the facility as user-friendly as possible to attract up till 3000 users by a feeling of inclusiveness (we have pre-inserted some users).
Drupal & MySQL 5.x Cluster
I setup a MySQL 5.0 Cluster on a spare server with multiple Xen VMs and discovered that Drupal 6 (and most likely D7 as wel) as it exists today cannot function properly under the MySQL NDBCLUSTER engine. It seems that under the NDBCLUSTER engine (also known as NDB), D6 has a table called menu_router that fails to be converted.
I posted a bug report about it under the D6 platform as it is rather detailed, but I have an idea this will affect D7 as well.
http://drupal.org/node/391130
Bikeshed Showdown: Figure out a "one true" DBTNG syntax
I've heard various rumblings in #drupal from people who don't like the current DBTNG code style for one reason or another. Since PDO doesn't have coding standards, we've had to make up our own. Complaints range from it being inconsistent (which wouldn't shock me, since it was decided sort of piecemeal between random conversations between Larry and myself) to not being easily formatted in tools like Coder Format and emacs (which is a big problem) to just being kind of "icky." Not having this nailed down is actively blocking issues such as porting core files to DBTNG.
So let's have it out! Here's the current syntax. Can you do better? And why?
<?php
$result = db_query("SELECT name FROM {test} WHERE age = :age", array(':age' => 25));
db_insert('test_task')
->fields(array('pid', 'task', 'priority'))
->values(array(
'pid' => $john,
'task' => 'eat',
'priority' => 3,
))
->values(array(
'pid' => $john,
'task' => 'sleep',
'priority' => 4,
))
->execute();
?>Reserved word conflicts: how can we solve it?
According to research progress of http://drupal.org/node/371#comment-1123065, D7 core schema is now conflict with following keywords. Any idea about the solution? Should we revamp and avoid the use of these reserved words?
Simple object CRUD: a proposal
With Drupal 6, menu tokens are able to automatically load database records given an object id, this is a great feature, however this requires developers to implement 'load functions' for loading their records. Those 'load functions' are often just a wrapper around 'SELECT * from {mytable} WHERE mykey = %d'.
We could do better, and allow automatically load operations, and even better, enable automatic basic CRUD.
Storing custom fields in users table - anyone doing this?
user.module has long supported storing custom fields in its table. values in those fields are automatically loaded into $user and saved during hook_user('insert'|'update').
has anyone used this feature in d6? i cam considering doing so for a high performance site where avoiding the join is helpful. with hook_scema_alter() we now have a clean wayto extend tables so i am feeling like this is a reasonable feature to use in custom code. i still would not recommend it for contrib code.
Database spotlight (moved)
(Note: I have moved the contents of this node to a sub-page of the http://drupal.org/community-initiatives/drupal-core section: http://drupal.org/node/361858 - webchick)
Databases: The Next Generation task list
With the new PDO-based database API now in core (yay!), there are a number of follow-up tasks that need to be taken care of. They were left out of the original patch for a variety of reasons, mostly keeping the already massive patch from becoming even more massive. :-)
Table "Node" Field "language"
Drupal 6.x. Table "node".
What should the value of the "language" field be if the displayed text is Chinese.
If a value is required, are there any other things that need to be done so that Chinese symbols are correctly displayed.
Any help appreciated.
Steve
http://prime357.org
ps. I've got a thread running at my site which I think this may be a part issue to it. As you can imagine it's becoming very confusing as all I see is either unicode or Chinese symbols (can't read Chinese).
Looking for Contributors - C++ (and other stuff in time)
Hope I'm not out of line with this request.
I'm now on the lookout for C++ contributors (and other like stuff in time). I started the site http://prime357.org, which is a separation from my personal blogging (http://superjacent.net - running) site, in early April this year. Too much geeky stuff was creeping into the running site.
Base 36 (Vancode) - leading digit/character
I hope this is the right area for this question which refers to the 'thread' field of the table 'comments'. I provide a non php solution to convert Wordpress data to Drupal. I recently became aware that the thread field is not a string of decimal numbers but is in fact a string of base 36 (Vancode) numbers. I've created the necessary functions to convert to and from base 36 format but I'm a little confused re - the leading digit/character.
Here is an excerpt from http://api.drupal.org/api/function/int2vancode/5
<
blockquote>
South Bay: Birds of a Feather session at MySQL Con followed by Sun & MySQL party (Both free attendance)
Join Amazon (Kieran Lal) and other Drupal community members and leaders at the Drupal Birds of a Feather session at the MySQL Conference & Expo on Wednesday, April 16th at 7:30pm. The BoF takes place in Ballroom “E” at the Santa Clara Convention Center. Afterwards, Sun will be giving away a Playstation 3 and Sun Fire X2100 M2 Server ($2,495) at their party next door. Wear your Drupal shirt!
More info about the conference:
http://en.oreilly.com/mysql2008
More info about the Sun party:
Some review and proposal about Drupal 7.x database stack
I start my Drupal + Oracle research since the end of Drupal 4.7 life cycle (around Oct 2006), based on my client's request. The project is still running, but I am not satisfy about its progress. After keep trace in Drupal database stack implementation for more than years, it is time for focusing on Drupal 7.x development.
So what are the changes since 4.7.x? And what will be happened for 7.x? I would like to share my research progress with you, and so let's brain storming for what's next :-)
DB support as contribute: is it a good idea?
Abstract
Drupal 6.0 is revamped with Schema API, so what's next for Drupal 7.x? PDO for sure! With this powerful data-access abstraction layer, workload will much reduced for DB abstraction layer designers and developers, and finally benefit our contribute developers and end users.
By the way, together with the decision of Drupal 7.x + PDO, there is also some voice about moving PostgreSQL (and so other potential databases support, e.g. Oracle, DB2, MSSQL, etc) support away from core, but contribute; on the other hand, add official SQLite support into Drupal core, together with MySQL.
Is this really a good idea? Or even if it is possible? As an existing Drupal + PostgreSQL users, what will this affect your daily work? As a potential customer of Drupal + Oracle/DB2/MSSQL/etc, is this a good new for you, or just an evil? I would like to provide some brief idea for you within this article.
Issues Need Review for Enhance Cross Database Compatibility
Enhance cross database compatibility is important for our Drupal Core, especially when we are going to ship D7 with PHP5.2.x PDO implementation. BTW, this will require number of individual patches, so your help and review are required - add it to the top list with a brief description and an estimate of the time to review. Once reviewed, move the issues to the bottom "reviewed" list, perhaps with your name attached.










