Welcome to the nuBuilder Forums!
Register and log in to access exclusive forums and content available only to registered users.
Register and log in to access exclusive forums and content available only to registered users.
Problems migrating a nuBuilder2 database.
-
- Posts: 37
- Joined: Sun Apr 21, 2013 10:58 pm
Problems migrating a nuBuilder2 database.
In need to upgrade a database developed at the very end of nuBuilder2-era to nuBuilder4 (no more support for PHP5.3 on new server).
Installing nuBuilder4 and setting up against a database went OK.
Experimenting building a form using fast form works OK, on both existing table, and non-existing table (nuBuilder reates the table for me).
But it is when I import the data from the old database --- that is --- all non-zzz-tables, my problems start.
I can still create a fast form on non-existing tables so a new table is created.
But, I'm unable to use fast form to create a form on any of the imported tables. I just get an empty page when i click the button created.
Also tried to create a form manually, but I cannot find a way to add a button to launch it, or reconfigre an existing button to launch it.
Anyone having an idea?
Installing nuBuilder4 and setting up against a database went OK.
Experimenting building a form using fast form works OK, on both existing table, and non-existing table (nuBuilder reates the table for me).
But it is when I import the data from the old database --- that is --- all non-zzz-tables, my problems start.
I can still create a fast form on non-existing tables so a new table is created.
But, I'm unable to use fast form to create a form on any of the imported tables. I just get an empty page when i click the button created.
Also tried to create a form manually, but I cannot find a way to add a button to launch it, or reconfigre an existing button to launch it.
Anyone having an idea?
-
- Posts: 37
- Joined: Sun Apr 21, 2013 10:58 pm
Re: Problems migrating a nuBuilder2 database.
Looks like, when I try do create a browse/edit form using fast form on an imported table.
The button is created, in the Home/Fast form area.
The edit form objects are created in the zzzsys_object table.
But there is no entry for the form in the zzzsys_form table.
Bug?
The button is created, in the Home/Fast form area.
The edit form objects are created in the zzzsys_object table.
But there is no entry for the form in the zzzsys_form table.
Bug?
-
- Posts: 785
- Joined: Sun Oct 14, 2018 11:25 am
Re: Problems migrating a nuBuilder2 database.
agnar,agnar wrote: The edit form objects are created in the zzzsys_object table.
But there is no entry for the form in the zzzsys_form table.
Bug?
I can't reproduce this, it works all fine for me. Do you get any rows back when you execute this SQL query on your database?
Code: Select all
SELECT * FROM zzzzsys_form WHERE zzzzsys_form_id NOT LIKE 'nu%'
-
- Posts: 37
- Joined: Sun Apr 21, 2013 10:58 pm
-
- Posts: 37
- Joined: Sun Apr 21, 2013 10:58 pm
Re: Problems migrating a nuBuilder2 database.
I'm noticing that nuBuilder4 gerenates id fields of varchar(25) for tables it generates itself.
Where as my imported tables have id fields of varchar(15).
A workaround seems to be to first generate the forms on an empty database, so nuBuilder will generate the tables.
Then drop the tables these tables, and instead import the tables from the old project.
At least it seemed to work on a test case...
Where as my imported tables have id fields of varchar(15).
A workaround seems to be to first generate the forms on an empty database, so nuBuilder will generate the tables.
Then drop the tables these tables, and instead import the tables from the old project.
At least it seemed to work on a test case...
Re: Problems migrating a nuBuilder2 database.
agnar,
A normally generated nuBuilder Forte ID is 15 characters long.
So you should not need to change your table's primary keys' widths.
The exception to this is some system IDs are prefixed with "nu" and therefore 17 long . eg. "nu5a72a0fce65fea2"
Which shouldn't affect your tables.
If you would like to zip up one of your tables and attach it to the forum, I'll try it myself.
The other thing is, what collation etc is your database server creating?...
BTW you say you have a nuBuilder 2 application, but you refer to some tables being prefixed with 3 zs (zzzsys_). Version 2 has 2 zs.
Steven
A normally generated nuBuilder Forte ID is 15 characters long.
So you should not need to change your table's primary keys' widths.
The exception to this is some system IDs are prefixed with "nu" and therefore 17 long . eg. "nu5a72a0fce65fea2"
Which shouldn't affect your tables.
If you would like to zip up one of your tables and attach it to the forum, I'll try it myself.
The other thing is, what collation etc is your database server creating?...
BTW you say you have a nuBuilder 2 application, but you refer to some tables being prefixed with 3 zs (zzzsys_). Version 2 has 2 zs.
Steven
You do not have the required permissions to view the files attached to this post.
-
- Posts: 37
- Joined: Sun Apr 21, 2013 10:58 pm
Re: Problems migrating a nuBuilder2 database.
Unfortunately, our project and customer database must be kept confidential.
However, I'm pasting the sql from one of the (inocent) tables here (cannot upload .txt or .sql files).
And I'm poor at counting: The nuBuilder tables have two z's of course.
However, I'm pasting the sql from one of the (inocent) tables here (cannot upload .txt or .sql files).
Code: Select all
-- phpMyAdmin SQL Dump
-- version 3.5.1
-- http://www.phpmyadmin.net
--
-- Host: localhost
-- Generation Time: Feb 06, 2018 at 10:52 AM
-- Server version: 5.1.73-1-log
-- PHP Version: 5.3.3-7+squeeze19
SET SQL_MODE="NO_AUTO_VALUE_ON_ZERO";
SET time_zone = "+00:00";
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
--
-- Database: `nuEpos2`
--
-- --------------------------------------------------------
--
-- Table structure for table `project_status`
--
CREATE TABLE IF NOT EXISTS `project_status` (
`project_status_id` varchar(15) NOT NULL,
`prs_order` int(2) NOT NULL,
`prs_name` varchar(40) NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
--
-- Dumping data for table `project_status`
--
INSERT INTO `project_status` (`project_status_id`, `prs_order`, `prs_name`) VALUES
('15175ad475671c', 10, 'Prospekt'),
('15175ad7d94334', 20, 'Tilbud gitt'),
('15175add80a7b1', 30, 'Tilbud akseptert'),
('15175af01df38f', 40, 'I arbeid'),
('15175af1c7bd1f', 50, 'Levert'),
('15175af59214d8', 60, 'Leveranse akseptert, ikke fakturert'),
('15175af83af79a', 70, 'Levert og fakturert'),
('15175afad63dae', 80, 'Avsluttet, faktura betalt'),
('15175afe08b9e5', 90, 'Avsluttet, faktura tapt'),
('15175b0029a2c5', 100, 'Prosjekt tapt'),
('15406f39e68a8b', 45, 'Sendt til trykkeriet'),
('15954f478385e4', 35, 'På vent');
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
-
- Posts: 785
- Joined: Sun Oct 14, 2018 11:25 am
Re: Problems migrating a nuBuilder2 database.
agnar,
I was able to reproduce what you are seeing (or not seeing) and the solution is to add a primary key to your table:
After that, (maybe logout and login first), build the form again using "Form Builder". Then you should see the Browse and Edit Form.
I was able to reproduce what you are seeing (or not seeing) and the solution is to add a primary key to your table:
Code: Select all
ALTER TABLE `project_status` ADD PRIMARY KEY(`project_status_id`);
You do not have the required permissions to view the files attached to this post.
-
- Posts: 37
- Joined: Sun Apr 21, 2013 10:58 pm
-
- Posts: 785
- Joined: Sun Oct 14, 2018 11:25 am