Search Results

A stored procedure would look something like this: DELIMITER $$ DROP PROCEDURE IF EXISTS insertEmployee$$ CREATE PROCEDURE insertEmployee (IN NewName VARCHAR(6)) BEGIN DECLARE CountStuff VARCHA …

I have three tables: forms which contains basic information about a form form_parts which contains information about a certain input field and has a FK to forms (each form parts must have one form_i …

I have to get "relevant" results from a table by joining it on another table and filtering the results on parent id and current id, this all goes fine until your current id is either the first or the …

I'm trying to select different types of data depending on a payment method which is a simple intersection table with columns "id" (INT PK) , "customer_id" (INT FK), "payment_method_id" (INT FK) and "d …

In the end what I did was select multiple times instead of just once, so for each result that I had I selected the next date_changed to get the period of time in between the two rows and when I had al …

You should revise your table structure. You are trying to put too many different things into one table. What you could do is have multiple tables like so: Table: site Has an ID and all other detai …

Run this query: UPDATE tablename SET textname = "" WHERE textname IS NULL after running that you can change the table structure so it does not allow null values anymore. I recommend checking the cod …

You could use a cron job to connect to the existing database, make a backup of the table, select the rows you need to move (over one week old) disconnect from the sql server, connect to the new serve …

I currently have this SQL statement (I'm using MySQL): SELECT CONCAT_WS( ', ', count(DISTINCT CONCAT(emailaddress, '_', e.id)), ( SELECT GROUP_CONCAT(items SEPARATOR '; ') as OneTimeItems …

error 1366 incorrect integer value: '""' for column 'word_id' at row 3 This error is logical, basically, an empty string is not a number. That's the first problem. Also I tried using null, quotes, …

I've built a covering index for a pretty big query which has already halved the select time. Now, all the columns are just INT(11)'s so there isn't a problem there but one of the columns is a VARCHAR …

So we have this VARCHAR(255) column called code, which is a string of varying size we use in a WHERE clause. Doing this search slows the query down by about 300ms and since the query is run a few hun …