Connect TC2 to MySQL database at startup
ClosedPublic
Actions

Authored by dereckson on Nov 22 2017, 01:50.

Tags

None

Referenced Files

	F30667671: D1243.id3195.diff
	Mon, May 25, 23:11

	F30646596: D1243.id.diff
	Mon, May 25, 19:07

	Unknown Object (File)
	Sun, May 24, 10:29

	Unknown Object (File)
	Sat, May 23, 06:56

	Unknown Object (File)
	Fri, May 22, 11:50

	Unknown Object (File)
	Tue, May 19, 09:19

	Unknown Object (File)
	Mon, May 18, 21:41

	Unknown Object (File)
	Mon, May 18, 21:13

View All Files

Subscribers

None

Details

Reviewers

dereckson

Commits

rVIPERcf06f027f7f8: Connect TC2 to MySQL database at startup

Summary

This is a follow-up for be5e31ed.

As the onload procedure is now used
for a non destructive task, commands
with crash risk are located to a new
'launch' proc.

Test Plan

.tcl onload

Diff Detail

Repository

rVIPER ViperServ scripts

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

dereckson created this revision.Nov 22 2017, 01:50

Harbormaster completed remote builds in B1972: Diff 3194.Nov 22 2017, 01:50

dereckson accepted this revision.Nov 22 2017, 01:53

This revision is now accepted and ready to land.Nov 22 2017, 01:53

Closed by commit rVIPERcf06f027f7f8: Connect TC2 to MySQL database at startup (authored by dereckson). · Explain WhyNov 22 2017, 02:01

This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

Path

Size

TC2/

Time.tcl

8 lines

Diff 3195

View Options

Connect TC2 to MySQL database at startupClosedPublicActions