Nice to see open-source software showing up in the tourism industry,
which I’ve always >imagined to be proprietary-application hell.
Pretty much everything we do is OS, we use ezpublish for our website,
for example, and Linux for our server. If I could find a good
reserverations system that was OS I would love it.
I just altered the tickets table so the default was 1000. I think it
would be a good way to set it up initially.
[mailto:email@example.com] On Behalf Of Rich Lafferty
Sent: Monday, December 09, 2002 11:43 AM
To: RT Users mailing list
Subject: Re: [rt-users] Changes to system
1: We are implementing RT for handling booking enquiries and general
enquiries from tourists.
3: I’d love to be able to set a start number for tickets, I don’t
like starting at “#1”, obviously I can do it in the database but it
would be a neat provision in the setup.
There is no initial setting in the install Makefile for the starting
number of the tickets, so the database trick is what you’ll need to
make do with
More importantly, RT simply asks the database for the next ticket
number, starting or otherwise.
For what it’s worth, the database trick for MySQL with MyISAM tables is
ALTER TABLE Tickets AUTO_INCREMENT = new_starting_id;
With InnoDB tables, that isn’t supported but you can get the same
feature with something like (off the top of my head!)
ALTER TABLE Tickets id int not null; -- removed "auto_increment"
INSERT INTO TICKETS (id) VALUES (new_starting_id);
ALTER TABLE Tickets id int not null auto_increment;
DELETE FROM TICKETS WHERE id = new_starting_id;
(If I remember my password, I’ll test and faq that.)
Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus!
http://www.lafferty.ca/ | http://zapatopi.net/treeoctopus.html
rt-users mailing list
Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm